How can I rebase without destroying changeset metadata?

[Steve Barnes]

On 14/01/13 16:19, Patrick Mézard wrote:
> On Mon, Jan 14, 2013 at 4:53 PM, Mads Kiilerich <mads at kiilerich.com> wrote:
>> On 01/14/2013 12:43 PM, dukeofgaming wrote:
>>
>> Yeah, nope, not there.
>>
>>
>> That sounds like a bug.
> Actually, that was by design: some extra fields can be safely moved,
> other cannot (branch name for instance). At API level you can register
> a callback to filter the fields you want but not at CLI level. Mads
> suggested the default behaviour (not rebasing fields) could be changed
> to rebase them always. I am afraid this comes a little too late and
> might be surprising for many extensions.
>
> That said, I got bitten by the very same problem in hgsubversion,
> though it can be fixed there.
> --
> Patrick Mezard
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
>
>
Are there any details of the fix on subversion available?  Currently 
looking a trying to port a set of subversion repositories to hg, (with 
svn:externs), so I will, I think, need to do some rebasing after 
introducing the subrepositories, ignores, etc.


-- 
Steve /Gadget/ Barnes
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20130114/426e393f/attachment-0002.html>