From: Jakub Narebski <jnareb@gmail.com>
To: Theodore Tso <tytso@mit.edu>
Cc: davidb@quicinc.com, Bryan Donlan <bdonlan@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Dividing up a large merge.
Date: Wed, 15 Jul 2009 06:39:46 -0700 (PDT) [thread overview]
Message-ID: <m31voiuktb.fsf@localhost.localdomain> (raw)
In-Reply-To: <20090715122828.GA6570@mit.edu>
Theodore Tso <tytso@mit.edu> writes:
> Yeah, that's another prime argument for maintaining your changes as a
> patch queue. I use a combination of quilt plus git.
Why not StGit, or Guilt, or TopGit?
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-07-15 13:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 23:32 Dividing up a large merge davidb
2009-07-15 0:16 ` Bryan Donlan
2009-07-15 0:29 ` davidb
2009-07-15 0:34 ` Avery Pennarun
2009-07-15 1:19 ` davidb
2009-07-15 1:29 ` Douglas Campos
2009-07-15 1:32 ` Avery Pennarun
2009-07-15 12:28 ` Theodore Tso
2009-07-15 13:39 ` Jakub Narebski [this message]
2009-07-15 16:07 ` Theodore Tso
2009-07-15 14:47 ` Larry D'Anna
2009-07-15 18:57 ` Daniel Barkalow
2009-07-15 21:01 ` davidb
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=m31voiuktb.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=bdonlan@gmail.com \
--cc=davidb@quicinc.com \
--cc=git@vger.kernel.org \
--cc=tytso@mit.edu \
/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).