[darcs-users] [issue938] darcs rebase

[Petr Rockai]

Hi,

Eric Kow <bugs at darcs.net> writes:
> Things I would use a hypothetical darcs rebase for.  This would clearly be an
> unsafe command in the sense of darcs-amend, but I think we can come up with
> enough scenarios to demonstrate that such a command would be useful in practice
> (and used often enough to not want to do by hand).
I actually once coded this to revise history of some of my
repos. Unfortunately, it appears that I have erased the patched version of
darcs when cleaning up my $HOME. : - (

I have added a "coerce" command, akin to pull, that took 2 remote repositories:
say "base" and "remote". What it did was take the patches in "remote" but not
in "base" and add them to current repo, regardless of context. It was only safe
if "base" and current were in exactly the same context (meaning same pristine
content, which could in theory be enforced to make the command fairly safe,
just history-altering).

I recall it wasn't particularly hard to implement, and if there's some sort of
consensus that such a feature would be welcome upstream, I could try to
re-create it. I have found it useful a few times in the past...

Yours,
    Petr.

PS: Thinking of that now, it might run into problems if the structure of the
patches was more than a little different between "base" and current...

-- 
Peter Rockai | me()mornfall!net | prockai()redhat!com
 http://blog.mornfall.net | http://web.mornfall.net

"In My Egotistical Opinion, most people's C programs should be
 indented six feet downward and covered with dirt."
     -- Blair P. Houghton on the subject of C program indentation