On Fri, Mar 4, 2011 at 1:29 AM, anatoly techtonik <[email protected]> wrote:
> I tried maintaining clones. Without some kind of visual tool that > displays changesets from different clones in different colors, it is a > mess. If some revision from your clone is merged as a patch into main > repository, you will still have a different branches. They can only > merge your branch, but you probably have a lot of other stuff in this > branch. There is no such thing as independent patches - there is still > history line, and even subsequent commits in your clone are completely > unrelated, you still don't have an option to merge just related > commits and mark them as merged. That's my understanding how Mercurial > works and I am afraid there is no cherry picking to help with keeping > modifications in sync with upstream. So it is better to keep separate > patches. I recommend the mq extension for those problems: http://mercurial.selenic.com/wiki/MqExtension -- Radomir Dopieralski, http://sheep.art.pl _______________________________________________ pydotorg-www mailing list [email protected] http://mail.python.org/mailman/listinfo/pydotorg-www
