From: "L. A. Walsh" <lkml@tlinx.org>
To: Chris Wright <chrisw@osdl.org>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: RFC: 2.6.release.patchlevel: Patch against 2.6.release[.0] ?
Date: Wed, 30 Mar 2005 18:20:01 -0800 [thread overview]
Message-ID: <424B5E51.2040709@tlinx.org> (raw)
In-Reply-To: <20050329230436.GQ28536@shell0.pdx.osdl.net>
Chris Wright wrote:
> The patches on kernel.org in v2.6/ are already against the base (i.e.
> patch-2.6.11.6.bz2 is against 2.6.11). The patches in v2.6/incr/
> are incremental between -stable releases (i.e. patch-2.6.11.5-6.bz2 is
> against 2.6.11.5).
----
I see. I had looked at the "Changelog" page on the www.kernel.org home
page and only saw changes from 2.6.11.5->2.6.11.6 documented. I thought that
the Changelog documented the changes that were in the patch.
Maybe Changlog's that only document the current increment should be in the
"incr" directory as well and be named "Changelog-2.6.11.5-6" (for the current
change log, while a cumulative change log from the base version should
be kept in the v2.6 dir?
I think having the Changelog link on the main page only documenting
the latest "incr", but having the patch containing everything from the base is
confusing. Am I the only one who might expect the Changelog to document what is
in the given increment, but the associated patch includes everything since the base?
It's a "nit", I know, but I prefer having the change-log and patch to match
w/respect to content.
Linda
prev parent reply other threads:[~2005-03-31 2:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 22:51 RFC: 2.6.release.patchlevel: Patch against 2.6.release[.0] ? L. A. Walsh
2005-03-29 22:58 ` Randy.Dunlap
2005-03-29 23:03 ` Dave Hansen
2005-03-29 23:04 ` Chris Wright
2005-03-31 2:20 ` L. A. Walsh [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=424B5E51.2040709@tlinx.org \
--to=lkml@tlinx.org \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.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