From: Ralf Baechle <ralf@linux-mips.org>
To: "M. Warner Losh" <imp@bsdimp.com>
Cc: daniel.j.laird@nxp.com, linux-mips@linux-mips.org
Subject: Re: Move arch/mips/philips to arch/mips/nxp
Date: Thu, 28 Feb 2008 16:10:47 +0000 [thread overview]
Message-ID: <20080228161047.GA10704@linux-mips.org> (raw)
In-Reply-To: <20080228.090058.-126817608.imp@bsdimp.com>
On Thu, Feb 28, 2008 at 09:00:58AM -0700, M. Warner Losh wrote:
> Are the references to BitKeeper still relevant here?
Vaguely. A while ago bk was in common use in the Linux community. The
licenses for bitkeeper were withdrawn around April 2005 so it's probably
time to remove them.
> >> Bear in mind that the Subject: of your email becomes a
> >> globally-unique identifier for that patch. It propagates all the
> >> way into BitKeeper. The Subject: may later be used in developer
> ------------^^^^^^^^^
> >> discussions which refer to the patch. People will want to google
> >> for the patch's Subject: to read discussion regarding that patch.
>
> and
>
> >> Do not refer to earlier patches when changelogging a new version of
> >> a patch. It's not very useful to have a bitkeeper changelog which
> -------------------------------------------^^^^^^^^^
> >> says "OK, this fixes the things you mentioned yesterday". Each
> >> iteration of the patch should contain a standalone changelog. This
> >> implies that you need a patch management system which maintains
> >> changelogs. See below.
>
> and
>
> >> Don't bother mentioning what version of the kernel the patch
> >> applies to ("applies to 2.6.8-rc1"). This is not interesting
> >> information - once the patch is in bitkeeper, of _course_ it
> --------------------------------------^^^^^^^^^
> >> applied, and it'll probably be merged into a later kernel than the
> >> one which you wrote it for.
Akpm wrote that. I wonder if he's got an updated version of this.
Ralf
prev parent reply other threads:[~2008-02-28 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 10:50 Move arch/mips/philips to arch/mips/nxp Daniel Laird
2008-02-28 9:42 ` Ralf Baechle
2008-02-28 16:00 ` M. Warner Losh
2008-02-28 16:10 ` Ralf Baechle [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=20080228161047.GA10704@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=daniel.j.laird@nxp.com \
--cc=imp@bsdimp.com \
--cc=linux-mips@linux-mips.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