[PATCH 2 of 2 V8] update: fix bare --clean to work on new branch (issue5003) (BC)

Matt Mackall mpm at selenic.com
Fri Apr 15 16:08:48 EDT 2016


On Wed, 2016-04-13 at 11:31 +0100, Simon Farnsworth wrote:
> On 13/04/2016 09:48, liscju wrote:
> > 
> > # HG changeset patch
> > # User liscju <piotr.listkiewicz at gmail.com>
> > # Date 1459834201 -7200
> > #      Tue Apr 05 07:30:01 2016 +0200
> > # Node ID dece0d6bc1442e50db920cd6ee04bebf786cddd1
> > # Parent  cabc4e5224db4d4f02e4460f4349df2e7ffd2e52
> > update: fix bare --clean to work on new branch (issue5003) (BC)
> > 
> > Before this commit bare update --clean on newly created branch
> > resulted in updating to the parent. After applying this commit bare
> > update --clean results in updating to the max head of the parents
> > branch.
> > 
> Again, "this commit" is implied; you can reword this in a simpler 
> fashion with something like "bare update --clean on a newly created 
> branch updates to the parent commit, even if there are later commits on 
> the parent commit's branch. Update to the latest head on the parent 
> commit's branch instead".

I've further tweaked this to:

Bare update --clean on a newly created branch resulted in updating to          
the parent, even if there were later commits on the parent branch. We           
now update to the latest head of the parent branch instead.                     

These are queued for default, thanks.

(Looks like this message was sitting unsent on my desktop. Since pushing it,
we've had test breakage + a follow-up fix fro Yuya you should look at.)

-- 
Mathematics is the supreme nostalgia of our time.



More information about the Mercurial-devel mailing list