How can I rebase without destroying changeset metadata?

[dukeofgaming]

Hi,

I am importing some Perforce stuff through Perfarce. Everything well until
I met with the delightful end of line problem since Perforce stores
everything as LF.

So I solved that with the EOL extension. Now I wanted to move the changeset
where I version the .hgeol file to the very beginning of the imported repo,
no problem:

$ hg update -C null
$ hg add .hgeol
$ hg commit -m "Adding .hgeol file"
$ hg id -n
123
$ hg rebase --source 0 --dest 123

So that leaves my newest commit as the root commit, effectively rewriting
history to include that .hgeol file with all changes... problem is now,
that I cannot pull from Perforce anymore, why?: there used to be a
"Perforce" field in my imported changesets and is now gone.

Now, I get why the changesets must be rewriten: to recalculate the hash
(surely among other things). But what I don't get is why does the Perfarce
metadata die with rebase?

Regards,

David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20130114/6d068f4b/attachment-0002.html>