[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnu-arch-users] how to recover from large conflicts?

From: Denys Duchier
Subject: [Gnu-arch-users] how to recover from large conflicts?
Date: Thu, 25 Sep 2003 00:25:55 +0200
User-agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3 (gnu/linux)

Here is another vexing first for me:

I have been tracking:


in my own branch:


Today, Charles needed to change the indentation of a large block of
code (to add exception handling).  Unfortunately, on my branch, I made
a small change in that block.  As a result, star-merge leaves behind a
fairly large .rej file.

What is a good strategy to recover from this?

I see the following possibilities:

1. bite the bullet and apply all the modifications by hand.
   this would certainly be fastest, but it is so intellectually
   unsatisfying that I'd like to investigate alternatives :-)

2. hack the .rej file to produce a diff that actually applies.  this
   file seems to be in unified diff diff format, but, when fed to
   patch, the latter complains about "missing header for context
   diff".  Is hacking this file a viable option?  I gave it a quick
   try and failed (and patch is woefully uninformative about possible

3. using "replay" maybe.  I wasn't able to figure out how to do this.
   I was thinking: replay the cduffy stuff (the old and the new that I
   wanted to star-merge), then replay my patches and fix what needs
   fixing.  Experimenting with replay only made me utterly confused.

4. temporarily back out the patch of mine that is probably causing
   trouble, star-merge, then re-apply my patch slightly tweaked.  I
   don't know how to do this either except by explicitly applying it
   backwards and then committing - is that the only option here?

I think I need some practical tutoring ("remedial arch" anyone? :-)


Dr. Denys Duchier
Équipe Calligramme

reply via email to

[Prev in Thread] Current Thread [Next in Thread]