From: Arnd Bergmann <arnd@arndb.de>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Chris Friesen <cfriesen@nortelnetworks.com>,
Andreas Dilger <adilger@clusterfs.com>,
Anton Blanchard <anton@samba.org>,
Linux kernel <linux-kernel@vger.kernel.org>,
paulus@samba.org
Subject: Re: offtopic: how to break huge patch into smaller independent patches?
Date: Wed, 15 Sep 2004 13:48:02 +0200 [thread overview]
Message-ID: <200409151348.07346.arnd@arndb.de> (raw)
In-Reply-To: <773640000.1095226032@[10.10.2.4]>
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
On Mittwoch, 15. September 2004 07:27, Martin J. Bligh wrote:
> Personally I find source control tools utterly useless for exactly this
> reason. Akpm uses his own set of tools which someone packaged up as
> "quilt" I think. I have a similar set that works by patch number, his
> are controlled by a series file. Suggest you look at his tools - if he
> can manage a release every few days with several hundred patches in, they
> must work pretty well ;-)
Seconded. I just inherited an equally sized patch from another party
and started looking into quilt for this. It doesn't save you from
understanding the patch, but it works wonders reducing the overhead
of doing the split once you know what you want to end up with.
What I'm doing now is keeping the patch files from quilt in the
CVS tree that also contains the patched kernel itself.
Arnd <><
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-15 11:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 19:48 offtopic: how to break huge patch into smaller independent patches? Chris Friesen
2004-09-14 20:11 ` William Lee Irwin III
2004-09-14 20:12 ` Dave Jones
2004-09-14 22:12 ` J. Bruce Fields
2004-09-16 21:11 ` Matthias Urlichs
2004-09-16 21:21 ` Herbert Poetzl
2004-09-15 0:20 ` Anton Blanchard
2004-09-15 0:47 ` Martin J. Bligh
2004-09-15 1:24 ` Chris Friesen
2004-09-15 1:47 ` Andreas Dilger
2004-09-15 4:36 ` Chris Friesen
2004-09-15 5:27 ` Martin J. Bligh
2004-09-15 11:48 ` Arnd Bergmann [this message]
2004-09-15 23:05 ` Andrew Morton
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=200409151348.07346.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=adilger@clusterfs.com \
--cc=anton@samba.org \
--cc=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=paulus@samba.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