2008/7/8 Karl Hasselström <kha@treskal.com>:No, the sync command is a 3-way merge between the top of a remote patch, the top of the current patch (current HEAD actually) and the bottom of the remote patch as ancestor. It also has a mode to synchronise with a patch file and it applies the patch onto the bottom of the current patch and does the merging between patch tops afterwards. This is not ideal as I have to deal with safe conflicts several time (maybe adding git-rerere support would help). If you have better ideas for keeping two stacks in sync, I'm happy to accept them (or maybe just a different workflow). -- Catalin -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Greg KH | Og dreams of kernels |
| Jens Axboe | [PATCH 31/33] Fusion: sg chaining support |
| Arnd Bergmann | Re: finding your own dead "CONFIG_" variables |
| Mark Brown | [PATCH 2/2] Subject: natsemi: Allow users to disable workaround for DspCfg reset |
| Tony Breeds | [LGUEST] Look in object dir for .config |
git: | |
| Brian Downing | Re: Git in a Nutshell guide |
| John Benes | Re: master has some toys |
| Matthias Lederhofer | [PATCH 4/7] introduce GIT_WORK_TREE to specify the work tree |
| Alexander Sulfrian | [RFC/PATCH] RE: git calls SSH_ASKPASS even if DISPLAY is not set |
