From: Andrew Morton <akpm@osdl.org>
To: NeilBrown <neilb@cse.unsw.edu.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH md 0 of 12] Introduction
Date: Wed, 23 Mar 2005 01:52:54 -0800 [thread overview]
Message-ID: <20050323015254.2f2d316c.akpm@osdl.org> (raw)
In-Reply-To: <20050323164208.16240.patches@notabene>
NeilBrown <neilb@cse.unsw.edu.au> wrote:
>
>
> Andrew: Are you happy to keep collecting these as a list of patches
> (bugs followed by bug-fixes :-), or would it be easier if I merged all
> the bug fixes into earlier patches and just resent a small number of
> "add-functionality" patches??
What I'll generally do is to topologically sort the patches. Work out what
patch each of the new patches fix and then rename the patches to
name-of-the-patch-whcih-is-being-fixed-fix.patch.
So if you had
foo.patch
bar.patch
and then sent be "[patch] frob the nozzle"
I'd work out that this new patch is fixing foo.patch and I'd name it
"foo-fix.patch" and the sequence would become:
foo.patch
foo-fix.patch
bar.patch
and then at some time in the future I'll collapse foo-fix.patch,
foo-fix-fix.patch, etc into foo.patch.
Of course it doesn't always work out that simply ;)
In this case it's not clear that a tsort will work out right. I'll take a
look.
next prev parent reply other threads:[~2005-03-23 9:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-23 5:47 [PATCH md 0 of 12] Introduction NeilBrown
2005-03-23 5:47 ` [PATCH md 1 of 12] Check return value of write_page, rather than ignore it NeilBrown
2005-03-23 5:47 ` [PATCH md 3 of 12] Improve debug-printing of bitmap superblock NeilBrown
2005-03-23 5:47 ` [PATCH md 2 of 12] Enable the bitmap write-back daemon and wait for it NeilBrown
2005-03-23 5:47 ` [PATCH md 9 of 12] Make sure md bitmap is cleared on a clean start NeilBrown
2005-03-23 5:47 ` [PATCH md 5 of 12] Print correct pid for newly created bitmap-writeback-daemon NeilBrown
2005-03-23 5:47 ` [PATCH md 12 of 12] Allow md intent bitmap to be stored near the superblock NeilBrown
2005-03-23 5:47 ` [PATCH md 11 of 12] Allow md to update multiple superblocks in parallel NeilBrown
2005-03-23 5:47 ` [PATCH md 8 of 12] A couple of tidyups relating to the bitmap file NeilBrown
2005-03-23 5:47 ` [PATCH md 4 of 12] Minor code rearrangement in bitmap_init_from_disk NeilBrown
2005-03-23 5:47 ` [PATCH md 7 of 12] Don't skip bitmap pages due to lack of bit that we just cleared NeilBrown
2005-03-23 5:47 ` [PATCH md 6 of 12] Call bitmap_daemon_work regularly NeilBrown
2005-03-23 5:47 ` [PATCH md 10 of 12] Fix bug when raid1 attempts a partial reconstruct NeilBrown
2005-03-23 9:52 ` Andrew Morton [this message]
2005-03-23 10:12 ` [PATCH md 0 of 12] Introduction Andrew Morton
2005-03-23 17:53 ` Lars Marowsky-Bree
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=20050323015254.2f2d316c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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).