git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Stacked GIT 0.3 (now more Quilt-like)

From
Rrandy_dunlap <rdunlap@xenotime.net>
Date
Jul 4, 2005, 17:09 UTC
Message-ID
<20050704100950.393630e8.rdunlap@xenotime.net>
In-Reply-To
<m3y88m21ln.fsf@telia.com>
On 04 Jul 2005 14:32:36 +0200 Peter Osterlund wrote:
| Catalin Marinas <catalin.marinas@gmail.com> writes:
| 
| > On Sun, 2005-07-03 at 14:38 +0200, Peter Osterlund wrote:
| > > Catalin Marinas <catalin.marinas@gmail.com> writes:
| > > > I know that using -A gives a more detailed output in case of a conflict.
| > > > The problem is that you will get a conflict even if the changes are
| > > > identical, making it impossible to detect when a patch was merged
| > > > upstream.
| > > 
| > > OK, I see. How about using wiggle instead?
| > > 
| > >         http://cgi.cse.unsw.edu.au/~neilb/source/wiggle/
| > > 
| > > That's what patch-utils uses if you run "pushpatch -m". wiggle is also
| > > a lot smarter than diff3, so there will be fewer cases that result in
| > > a conflict. Maybe a parameter to "stg push" could enable wiggle mode.
| > 
| > I haven't used wiggle before but I will give it a try (though I prefer
| > such a tool not to be too smart since it might make mistakes). Anyway, I
| > will make this configurable, i.e. you could put something like below in
| > the .stgitrc file:
| > 
| > merger = 'diff3 -m -E %(branch1)s %(ancestor)s %(branch2)s'
| > 
| > or
| > 
| > merger = 'wiggle -m %(branch1)s %(ancestor)s %(branch2)s'
| > 
| > > Is there a way in StGIT to undo a push that results in a large mess of
| > > conflicts?
| > 
| > Good point. No, there isn't yet. I will think about an undo command. At
| > the moment, the old top and bottom ids of a patch are saved so that the
| > patch before the merge can be retrieved but there isn't any command to
| > make use of them.
| 
| I agree with the other comments, it's probably not wise to rely on
| wiggle, and wiggle sometimes makes a mess. However, it often does the
| right thing, and with a configurable merge program and an undo
| function, this should not be a problem. Just undo and try again if you
| don't like the result.

You could try Chris Mason's 'rej' as well. ftp://ftp.oregonstate.edu/pub/suse/people/mason/rej/rej-0.15.tar.gz (from one mirror site)

--- ~Randy

Previous: Peter OsterlundNext: Catalin Marinas
Message 8 of 16 in “Stacked GIT 0.3 (now more Quilt-like)”
  1. Catalin MarinasJun 28, 2005
  2. Peter OsterlundJul 3, 2005
  3. Catalin MarinasJul 3, 2005
  4. Peter OsterlundJul 3, 2005
  5. Catalin MarinasJul 3, 2005
  6. Martin LanghoffJul 4, 2005
  7. Peter OsterlundJul 4, 2005
  8. randy_dunlapJul 4, 2005
  9. Catalin MarinasJul 4, 2005
  10. Catalin MarinasJul 6, 2005
  11. Peter OsterlundJul 7, 2005
  12. Catalin MarinasJul 7, 2005
  13. Peter OsterlundJul 8, 2005
  14. Junio C HamanoJul 8, 2005
  15. Peter OsterlundJul 8, 2005
  16. Catalin MarinasJul 8, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.