git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Jan Engelhardt" <jengelh@computergmbh.de>
Cc: git <git@vger.kernel.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Josef Sipek" <jsipek@fsl.cs.sunysb.edu>
Subject: Re: [ANNOUNCE] Stacked GIT 0.14.2
Date: Mon, 24 Mar 2008 23:24:20 +0000	[thread overview]
Message-ID: <b0943d9e0803241624ne83602emc1fb4727402555d3@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.1.10.0803242113070.9368@fbirervta.pbzchgretzou.qr>

On 24/03/2008, Jan Engelhardt <jengelh@computergmbh.de> wrote:
> On Monday 2008-03-24 20:59, Catalin Marinas wrote:
>
>  > Stacked GIT 0.14.2 release is available from http://www.procode.org/stgit/.
>  >
>  > StGIT is a Python application providing similar functionality to Quilt
>  > (i.e. pushing/popping patches to/from a stack) on top of GIT.
>
>
> I always wondered what the difference between stgit and guilt is.
>  Does anyone have a comparison up?

There was a thread last year:

http://kerneltrap.org/mailarchive/git/2007/6/14/249310

I don't follow the guilt development to be able to comment. They are
pretty similar regarding patch management but it's probably best to
try both and see which tool you like. StGIT might have a few more
features as it was around for longer (e-mail templates, patch
synchronisation between branches etc.) but guilt seems actively
developed as well.

I might be wrong here but I'm not sure whether guilt uses three-way
merging when pushing a patch or just a two-way diff apply. The
three-way merging has several advantages in dealing with conflicts.

-- 
Catalin

  parent reply	other threads:[~2008-03-24 23:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-24 19:59 [ANNOUNCE] Stacked GIT 0.14.2 Catalin Marinas
2008-03-24 20:15 ` Jan Engelhardt
2008-03-24 20:33   ` Rene Herman
2008-03-24 20:43     ` Junio C Hamano
2008-03-24 22:31       ` Rene Herman
2008-03-24 22:50         ` Catalin Marinas
2008-03-24 23:23           ` Rene Herman
2008-03-24 23:40             ` Catalin Marinas
2008-03-24 23:55       ` Josef Sipek
2008-03-25  9:50         ` slurping in guilt, was " Johannes Schindelin
2008-03-26 21:24           ` Junio C Hamano
2008-03-27  0:03             ` Josef Sipek
2008-03-24 23:55       ` Catalin Marinas
2008-03-24 23:24   ` Catalin Marinas [this message]
2008-03-24 23:39     ` Josef Sipek

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=b0943d9e0803241624ne83602emc1fb4727402555d3@mail.gmail.com \
    --to=catalin.marinas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jengelh@computergmbh.de \
    --cc=jsipek@fsl.cs.sunysb.edu \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).