Andrew's git
/
gitweb.git
/ diff
summary
|
log
|
commit
| diff |
tree
commit
grep
author
committer
pickaxe
?
re
update using-topic-branches
author
Luck, Tony
<tony.luck@intel.com>
Fri, 20 Jan 2006 19:00:18 +0000
(11:00 -0800)
committer
Junio C Hamano
<junkio@cox.net>
Fri, 20 Jan 2006 21:34:12 +0000
(13:34 -0800)
Update documentation to warn users not to create noise in then Linux
history by creating pointless "Auto-update from upstream" merge
commits.
Signed-off-by: Tony Luck <tony.luck@intel.com>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Documentation/howto/using-topic-branches.txt
patch
|
blob
|
history
raw
|
patch
|
inline
| side by side (parent:
e755578
)
diff --git
a/Documentation/howto/using-topic-branches.txt
b/Documentation/howto/using-topic-branches.txt
index b3d592fc3e1796643f8771bbd549ced5532d7a96..2c98194cb84d34bbcb5f3c0bc989728e46f7f9d3 100644
(file)
--- a/
Documentation/howto/using-topic-branches.txt
+++ b/
Documentation/howto/using-topic-branches.txt
@@
-9,7
+9,7
@@
GIT as a Linux subsystem maintainer.
-Tony
-Tony
-Last updated w.r.t. GIT
0.99.9f
+Last updated w.r.t. GIT
1.1
Linux subsystem maintenance using GIT
-------------------------------------
Linux subsystem maintenance using GIT
-------------------------------------
@@
-92,6
+92,14
@@
These can be easily kept up to date by merging from the "linus" branch:
$ git checkout test && git merge "Auto-update from upstream" test linus
$ git checkout release && git merge "Auto-update from upstream" release linus
$ git checkout test && git merge "Auto-update from upstream" test linus
$ git checkout release && git merge "Auto-update from upstream" release linus
+Important note! If you have any local changes in these branches, then
+this merge will create a commit object in the history (with no local
+changes git will simply do a "Fast forward" merge). Many people dislike
+the "noise" that this creates in the Linux history, so you should avoid
+doing this capriciously in the "release" branch, as these noisy commits
+will become part of the permanent history when you ask Linus to pull
+from the release branch.
+
Set up so that you can push upstream to your public tree (you need to
log-in to the remote system and create an empty tree there before the
first push).
Set up so that you can push upstream to your public tree (you need to
log-in to the remote system and create an empty tree there before the
first push).