From: Josef Sipek <jsipek@fsl.cs.sunysb.edu>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
git <git@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Stacked GIT 0.14.2
Date: Mon, 24 Mar 2008 19:39:52 -0400 [thread overview]
Message-ID: <20080324233952.GD32221@josefsipek.net> (raw)
In-Reply-To: <b0943d9e0803241624ne83602emc1fb4727402555d3@mail.gmail.com>
On Mon, Mar 24, 2008 at 11:24:20PM +0000, Catalin Marinas wrote:
> 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.
Right. Try both and use whatever you're happier with.
> 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.
It's still using two-way diff apply, but I'd like to implement a three-way
merge as a fallback.
Josef 'Jeff' Sipek.
--
The box said "Windows XP or better required". So I installed Linux.
prev parent reply other threads:[~2008-03-24 23:40 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
2008-03-24 23:39 ` Josef Sipek [this message]
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=20080324233952.GD32221@josefsipek.net \
--to=jsipek@fsl.cs.sunysb.edu \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=jengelh@computergmbh.de \
--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).