diff options
| author | Junio C Hamano <junio@hera.kernel.org> | 2008-08-10 03:55:58 +0000 |
|---|---|---|
| committer | Junio C Hamano <junio@hera.kernel.org> | 2008-08-10 03:55:58 +0000 |
| commit | faa1e50737bfc349e8315c99a2ed59182fd557b1 (patch) | |
| tree | 05ca5456c6a103f7632321128d3a325a68450748 /git-rerere.txt | |
| parent | b53db3ca58a8a65d8de3b9fa048d410757edc38f (diff) | |
| download | git-htmldocs-faa1e50737bfc349e8315c99a2ed59182fd557b1.tar.gz | |
Autogenerated HTML docs for v1.6.0-rc2-22-g71b9
Diffstat (limited to 'git-rerere.txt')
| -rw-r--r-- | git-rerere.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/git-rerere.txt b/git-rerere.txt index 89f321b41..64715c17d 100644 --- a/git-rerere.txt +++ b/git-rerere.txt @@ -90,15 +90,15 @@ One way to do it is to pull master into the topic branch: The commits marked with `*` touch the same area in the same file; you need to resolve the conflicts when creating the commit -marked with `+`. Then you can test the result to make sure your +marked with `{plus}`. Then you can test the result to make sure your work-in-progress still works with what is in the latest master. After this test merge, there are two ways to continue your work on the topic. The easiest is to build on top of the test merge -commit `+`, and when your work in the topic branch is finally +commit `{plus}`, and when your work in the topic branch is finally ready, pull the topic branch into master, and/or ask the upstream to pull from you. By that time, however, the master or -the upstream might have been advanced since the test merge `+`, +the upstream might have been advanced since the test merge `{plus}`, in which case the final commit graph would look like this: ------------ |