public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.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: Tue, 14 Sep 2004 22:36:38 -0600	[thread overview]
Message-ID: <4147C6D6.30508@nortelnetworks.com> (raw)
In-Reply-To: <20040915014711.GA30607@schnapps.adilger.int>

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.

Chris

  reply	other threads:[~2004-09-15  4:36 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 [this message]
2004-09-15  5:27           ` Martin J. Bligh
2004-09-15 11:48             ` Arnd Bergmann
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=4147C6D6.30508@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=adilger@clusterfs.com \
    --cc=anton@samba.org \
    --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