3 ms·
Mercurial tries to avoid the "rebasing public changes" problem with a new hg 2.1 feature called "phases" that tracks whether a changeset has been shared. Unfort
by cpeterso 14y ago
Mercurial tries to avoid the "rebasing public changes" problem with a new hg 2.1 feature called "phases" that tracks whether a changeset has been shared. Unfortunately, it is a little simple-minded because pushing to any other hg repo, even on your same machine, will mark the changeset as "public".
http://www.logilab.org/blogentry/88203 http://www.logilab.org/blogentry/88203
- mindajar 14y agoThat's not the case if the 'other' repo is configured as a non-publishing repository. http://mercurial.selenic.com/wiki/Phases#Publishing_Repository http://mercurial.selenic.com/wiki/Phases#Publishing_Reposito...