Ezio Melotti added the comment: > I think it would be good to have a separate subsection dedicated just > to the setting up portion of multiple clones with the share extension
I'm not sure that's necessary though, given how simple it is (enable share extension, "hg share source dest", repeat). The ideas are: 1) have a straightforward from-beginning-to-end overview in committing.rst, followed by a few sections that explain more in detail the most common steps (e.g. how to merge between different versions, how to solve merge conflicts, etc.); 2) list alternative approaches (e.g. multiple unshared clones) and "advanced" steps (e.g. deal with merge conflicts) in the FAQs; If you think all the approaches should be listed somewhere, we can always add a new FAQ later, but it shouldn't block this issue (and it shouldn't be in committing.rst). > One thing that is missing though, which I think is or was in a > current or previous version, is to put all the pull and update > commands in a batch file. The point of the share extension is that is no longer necessary to pull/push changesets between clones (the updates still are though). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14468> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
