From: Andrew Morton <akpm@osdl.org>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: adilger@clusterfs.com, mbligh@aracnet.com, anton@samba.org,
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 16:05:54 -0700 [thread overview]
Message-ID: <20040915160554.6d8350ca.akpm@osdl.org> (raw)
In-Reply-To: <4147C6D6.30508@nortelnetworks.com>
Chris Friesen <cfriesen@nortelnetworks.com> wrote:
>
> Andreas Dilger wrote:
>
> > Consider using a source-control tool next time ;-/.
>
> We used a source control tool. Its just not very useful when people do a port
> from one kernel version to the next and submit it as one giant patch against the
> new kernel rather than new versions of the original individual patches.
>
> I'm the one planning how to avoid this problem in our next development cycle.
>
What others said.
Once you apply those patches to your baseline tree you're dead. If your
primary revision-controlled objects are baseline+patch1+patch2+...+patchN
then life is much simpler when some smarty decides to uprev baseline.
prev parent reply other threads:[~2004-09-15 23:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 19:48 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
2004-09-15 23:05 ` Andrew Morton [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=20040915160554.6d8350ca.akpm@osdl.org \
--to=akpm@osdl.org \
--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
all inboxes | Powered by JetHome®