[issue3266] rebasing un-pushed changesets moves phase to public
bugs at mercurial.selenic.com
Mon Feb 13 14:44:40 CST 2012
New submission from Matthew Giannini <mgiannini at tridium.com>:
Per Matt's response to my post ("issue with rebasing and patches") on the mercurial list
serve, I am reporting the following bug:
On Mon, 2012-02-13 at 19:02 +0000, Giannini, Matthew wrote:
> I am observing that un-pushed changesets are being moved to phase "public" when they are
> I did the following steps:
> 1. Committed local changeset 100.
> 2. Pulled from master and got 2 new changesets (101, 102).
> 3. I don't want to merge my changeset because I want to avoid a merge turd, so I
rebase 100 on top of 102.
> 4. This works fine, but now my changeset (103) has been moved to phase "public".
title: rebasing un-pushed changesets moves phase to public
Mercurial issue tracker <bugs at mercurial.selenic.com>
More information about the Mercurial-devel