git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	Jan Engelhardt <jengelh@computergmbh.de>,
	git <git@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Josef Sipek <jsipek@fsl.cs.sunysb.edu>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [ANNOUNCE] Stacked GIT 0.14.2
Date: Tue, 25 Mar 2008 00:23:20 +0100	[thread overview]
Message-ID: <47E837E8.7000606@keyaccess.nl> (raw)
In-Reply-To: <b0943d9e0803241550k3ef0dbe8nae3b00bac34fa20@mail.gmail.com>

On 24-03-08 23:50, Catalin Marinas wrote:

> On 24/03/2008, Rene Herman <rene.herman@keyaccess.nl> wrote:
>> On 24-03-08 21:43, Junio C Hamano wrote:

>>  >> On 24-03-08 21:15, Jan Engelhardt wrote:

>>  >>> I always wondered what the difference between stgit and guilt is.
>>  >>> Does anyone have a comparison up?
>>  >> And I remember some mumblings about git growing quilt-like
>>  >> functionality itself. Anything on that?
>>  >
>>  > Not my mumbling
>>
>>
>> Believe it was Linus. Seem to remember him saying something about possibly
>> adding a native queues-like interface not too long ago but it's proving
>> impossible to google for.
> 
> It was Linus indeed, on the linux-arch mailing list:
> 
> http://www.mail-archive.com/linux-arch@vger.kernel.org/msg05012.html

Probably read it on linux-kernel but yes, that was the one, thanks much. 
Stored it as an interesting something -- used to use quilt and although I 
didn't much care for its linear nature when managing an entire tree, it 
probably works out well for private topic branches. Not overly sure of added 
practical value over git rebase, but I did like the simple nature of 
shuffling things around by just editing a series file back when I was using 
quilt. Keeps one on top of things, so to speak (<-- amusing play on words).

Moreover not too keen on using many tools do do one thing, so getting this 
inside git itself sounded like a possibly nice notion.

Rene.

  reply	other threads:[~2008-03-24 23:23 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 [this message]
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

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=47E837E8.7000606@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=catalin.marinas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jengelh@computergmbh.de \
    --cc=jsipek@fsl.cs.sunysb.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).