All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Osterlund <petero2@telia.com>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: GIT <git@vger.kernel.org>
Subject: Re: Stacked GIT 0.3 (now more Quilt-like)
Date: 03 Jul 2005 10:38:27 +0200	[thread overview]
Message-ID: <m3ekagp9mk.fsf@telia.com> (raw)
In-Reply-To: <1119994003.9631.6.camel@localhost.localdomain>

Catalin Marinas <catalin.marinas@gmail.com> writes:

> A new StGIT release is available from http://procode.org/stgit/
> 
> What's new in version 0.3:
>       * closer to the Quilt functionality
>       * there is only one commit object per patch which can be
>         indefinitely modified using the 'refresh' command. The commit
>         objects are stacked on top of the base and can also be accessed
>         via standard GIT commands
>       * no 'commit' command. Use 'refresh' instead
> 
> StGIT is a Python application providing similar functionality to Quilt
> (i.e. pushing/popping patches to/from a stack) on top of GIT. These
> operations are performed using GIT commands and the patches are stored
> as GIT commit objects, allowing easy merging of the StGIT patches into
> other repositories using standard GIT functionality.

This is good stuff and the 3-way merge really simplifies things.
However, if there is a merge conflict, you will basically be stuck
with a 2-way merge when resolving manually. It's usually much easier
if you can see all three version, so I think it's better to use -A
instead of -E in the diff3 command.

--- stgit-0.3/gitmergeonefile.py~	2005-06-28 14:15:22.000000000 +0200
+++ stgit-0.3/gitmergeonefile.py	2005-07-03 02:33:13.000000000 +0200
@@ -108,7 +108,7 @@
         # 3-way merge
         else:
             merge_ok = os.system('diff3 -L local -L older -L remote '
-                                 '-m -E %s %s %s > %s'
+                                 '-m -A %s %s %s > %s'
                                   % (src1, orig, src2, path)) == 0
 
             if merge_ok:

-- 
Peter Osterlund - petero2@telia.com
http://web.telia.com/~u89404340

  reply	other threads:[~2005-07-03  9:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-28 21:26 Stacked GIT 0.3 (now more Quilt-like) Catalin Marinas
2005-07-03  8:38 ` Peter Osterlund [this message]
2005-07-03 10:08   ` Catalin Marinas
2005-07-03 12:38     ` Peter Osterlund
2005-07-03 21:14       ` Catalin Marinas
2005-07-04  1:10         ` Horst von Brand
2005-07-04  6:27         ` Martin Langhoff
2005-07-04 12:32         ` Peter Osterlund
2005-07-04 17:09           ` randy_dunlap
2005-07-04 20:42           ` Catalin Marinas
2005-07-06 20:54           ` Catalin Marinas
2005-07-07 19:17             ` Peter Osterlund
2005-07-07 21:22               ` Catalin Marinas
2005-07-08  1:10 ` Peter Osterlund
2005-07-08  1:24   ` Junio C Hamano
2005-07-08  8:14     ` Peter Osterlund
2005-07-08  9:32       ` Catalin Marinas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3ekagp9mk.fsf@telia.com \
    --to=petero2@telia.com \
    --cc=catalin.marinas@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.