From: Willy Tarreau <willy@w.ods.org>
To: Peter Chubb <peter@chubb.wattle.id.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel patch release checklist available
Date: Thu, 26 Jun 2003 15:22:54 +0200 [thread overview]
Message-ID: <20030626132254.GA27843@alpha.home.local> (raw)
In-Reply-To: <16122.53870.710841.141793@wombat.chubb.wattle.id.au>
On Thu, Jun 26, 2003 at 09:01:02PM +1000, Peter Chubb wrote:
>
> After being burnt a few times in forgetting something that I should
> have done when releasing a patch against the kernel, I've created a
> Kernel Patch Release Checklist at
>
> http://www.gelato.unsw.edu.au/IA64wiki/PatchReleaseChecklist
Good idea. I think this should go into the Documentation directory.
I would personnaly add :
- "1.4.3 have you described side-effects you're aware of, or incompatibilities
or breakage of other patches ?"
- "1.5.2. Have you checked that your patch still applies without fuzz on latest
dev kernel ?" (which is not implied nor excused by 1.4.2).
Cheers,
Willy
next prev parent reply other threads:[~2003-06-26 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-26 11:01 Kernel patch release checklist available Peter Chubb
2003-06-26 13:22 ` Willy Tarreau [this message]
2003-06-26 19:24 ` David Mosberger
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=20030626132254.GA27843@alpha.home.local \
--to=willy@w.ods.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@chubb.wattle.id.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