Andrew's git
/
gitweb.git
/ diff
summary
|
log
|
commit
| diff |
tree
commit
grep
author
committer
pickaxe
?
re
Documentation: typos and small fixes in "everyday".
author
Junio C Hamano
<junkio@cox.net>
Sun, 18 Dec 2005 20:11:27 +0000
(12:11 -0800)
committer
Junio C Hamano
<junkio@cox.net>
Sun, 18 Dec 2005 20:11:27 +0000
(12:11 -0800)
Signed-off-by: Junio C Hamano <junkio@cox.net>
Documentation/everyday.txt
patch
|
blob
|
history
raw
|
patch
|
inline
| side by side (parent:
2247efb
)
diff --git
a/Documentation/everyday.txt
b/Documentation/everyday.txt
index df1e287999d501fa77ab8c86a464756a96ba3ef0..3ab9b916c290570518b568edef97a12ea2119408 100644
(file)
--- a/
Documentation/everyday.txt
+++ b/
Documentation/everyday.txt
@@
-211,10
+211,12
@@
$ git fetch --tags <8>
<1> repeat as needed.
<2> extract patches from your branch for e-mail submission.
<1> repeat as needed.
<2> extract patches from your branch for e-mail submission.
-<3> "pull" fetches from "origin" by default and merges.
-<4> look at the changes since last time we checked, only in the
+<3> "pull" fetches from "origin" by default and merges into the
+current branch.
+<4> immediately after pulling, look at the changes done upstream
+since last time we checked, only in the
area we are interested in.
area we are interested in.
-<5> fetch from a specific branch from a specific repository and
and
merge.
+<5> fetch from a specific branch from a specific repository and merge.
<6> revert the pull.
<7> garbage collect leftover objects from reverted pull.
<8> from time to time, obtain official tags from the "origin"
<6> revert the pull.
<7> garbage collect leftover objects from reverted pull.
<8> from time to time, obtain official tags from the "origin"
@@
-330,16
+332,18
@@
master, nor exposed as a part of a stable branch.
<8> and bundle topic branches still cooking.
<9> backport a critical fix.
<10> create a signed tag.
<8> and bundle topic branches still cooking.
<9> backport a critical fix.
<10> create a signed tag.
-<11> make sure I did not accidentally rew
ou
nd master beyond what I
+<11> make sure I did not accidentally rew
i
nd master beyond what I
already pushed out. "ko" shorthand points at the repository I have
at kernel.org, and looks like this:
already pushed out. "ko" shorthand points at the repository I have
at kernel.org, and looks like this:
-$ cat .git/remotes/ko
-URL: kernel.org:/pub/scm/git/git.git
-Pull: master:refs/tags/ko-master
-Pull: maint:refs/tags/ko-maint
-Push: master
-Push: +pu
-Push: maint
+ $ cat .git/remotes/ko
+ URL: kernel.org:/pub/scm/git/git.git
+ Pull: master:refs/tags/ko-master
+ Pull: maint:refs/tags/ko-maint
+ Push: master
+ Push: +pu
+ Push: maint
+In the output from "git show-branch", "master" should have
+everything "ko-master" has.
<12> push out the bleeding edge.
<13> push the tag out, too.
------------
<12> push out the bleeding edge.
<13> push the tag out, too.
------------
@@
-357,8
+361,8
@@
and maintain access to the repository by developers.
* gitlink:git-shell[1] can be used as a 'restricted login shell'
for shared central repository users.
* gitlink:git-shell[1] can be used as a 'restricted login shell'
for shared central repository users.
- * link:howto/update-hook-example.txt[update hook howto] has a
-
good
example of managing a shared central repository.
+link:howto/update-hook-example.txt[update hook howto] has a good
+example of managing a shared central repository.
Examples
Examples