From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@codesourcery.com>
Cc: Ulrich Weigand <uweigand@de.ibm.com>, gdb-patches@sourceware.org
Subject: Re: Managing long patch series
Date: Fri, 26 Oct 2007 19:26:00 -0000 [thread overview]
Message-ID: <20071026185634.GA31923@caradoc.them.org> (raw)
In-Reply-To: <m3d4v1d815.fsf@codesourcery.com>
On Fri, Oct 26, 2007 at 11:51:02AM -0700, Jim Blandy wrote:
> I've tried using quilt, but if one doesn't keep very careful track of
> what's going on things can get very tangled. The Emacs mode helped
> somewhat, but had other flaws, so I set it aside.
I usually do it with quilt plus the emacs mode now. What flaws? The
only one I've noticed as a real inconvenience is trouble adding new
files, but a talented Lisp hacker could probably fix it in moments.
It's still mildly error prone, but popping everything and doing cvs
diff is good at turning up anything I've missed.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-10-26 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 18:56 Jim Blandy
2007-10-26 19:26 ` Daniel Jacobowitz [this message]
2007-10-29 16:11 ` Jim Blandy
2007-10-27 8:11 ` Vladimir Prus
2007-10-29 15:15 ` Jim Blandy
2007-10-29 18:59 ` Ulrich Weigand
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=20071026185634.GA31923@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.com \
--cc=uweigand@de.ibm.com \
/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