Loosing revision history after rename and compress/rebase

Weichelt David J WeicheltDavid at JohnDeere.com
Tue Jan 7 17:12:42 UTC 2014


Thanks for the response... reply below...

From: Pierre-Yves David [mailto:pierre-yves.david at ens-lyon.org]
Sent: Friday, January 03, 2014 6:18 PM
To: Weichelt David J
Cc: mercurial at selenic.com; Albright Steve; Bogh Jason; Faber Ross
Subject: Re: Loosing revision history after rename and compress/rebase

On 01/03/2014 02:53 PM, Weichelt David J wrote:
I'm looking for support on this problem we have seen.  The scenario was confirmed with other developers and it perhaps needs to be fixed by the Mercurial community...  we don't know how to work around this.  Not cool to loose revision history from code that we are moving around and changing.

Steps to reproduce:

1.       Have a committed file with a revision history

2.       Hg rename the file from one directory to a new one (with renaming the file in my testing)

3.       Commit the changes

4.       Compress the changes (also can see same problem with rebase)

What do you mean by "compressing the change" ?

<David> THG has the ability to compress multiple changesets into one changeset.  I was referring to compressing multiples change which includes at the tip the rename changeset.


What kind of rebase command are you typing ?

<David> I'm using THG (right clicking on the changeset after updating to the base I want to rebase on).



5.       (optional) Strip the original changset that was compressed

6.       Notice that the revision history is missing on the new changeset

Do you mean that a log for the file is not including older revision for the previous name?

<David> Yes, I don't see any history for the file from before the rename (aka move), only 1 changset.


--
Pierre-Yves David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20140107/e95f2396/attachment-0002.html>


More information about the Mercurial mailing list