mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: oxymoron@waste.org, torvalds@osdl.org, akpm@osdl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] automate patch names in kernel versions
Date: Tue, 5 Aug 2003 12:33:49 -0700	[thread overview]
Message-ID: <20030805123349.6a3db1f9.rddunlap@osdl.org> (raw)
In-Reply-To: <20030805191718.GC970@matchmail.com>

On Tue, 5 Aug 2003 12:17:18 -0700 Mike Fedyk <mfedyk@matchmail.com> wrote:

| On Tue, Jul 29, 2003 at 03:44:19PM -0500, Oliver Xymoron wrote:
| > Perhaps times have changed enough that I can revive this idea from a
| > few years ago:
| > 
| > http://groups.google.com/groups?q=patchname+oxymoron&hl=en&lr=&ie=UTF-8&selm=fa.jif8l5v.1b049jd%40ifi.uio.no&rnum=1
| > 
| > <quote year=1999>
| > This four-line patch provides a means for listing what patches have
| > been built into a kernel. This will help track non-standard kernel
| > versions, such as those released by Redhat, or Alan's ac series, etc.
| > more easily.
| > 
| > With this patch in place, each new patch can include a file of the
| > form "patchname.[identifier]" in the top level source directory and
| > [identifier] will then be added to the kernel version string. For
| > instance, Alan's ac patches could include a file named patchdesc.ac2
| > (containing a change log, perhaps), and the resulting kernel would be
| > identified as 2.2.0-pre6+ac2, both at boot and by uname.
| > 
| > This may prove especially useful for tracking problems with kernels
| > built by distribution packagers and problems reported by automated
| > tools.
| > </quote>
| > 
| > The patch now appends patches as -name rather than +name to avoid
| > issues that might exist with packaging tools and scripts.
| 
| Has anything happened with this patch?
| 
| I for one would love it to be merged.

I saved it, as you did too apparently.
Looks nice to me as well.

--
~Randy

  reply	other threads:[~2003-08-05 19:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-29 20:44 Oliver Xymoron
2003-07-29 22:15 ` Eric Sandall
2003-07-29 23:40   ` Matt Mackall
2003-08-05 19:17 ` Mike Fedyk
2003-08-05 19:33   ` Randy.Dunlap [this message]
2003-08-05 20:10     ` Matt Mackall

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=20030805123349.6a3db1f9.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfedyk@matchmail.com \
    --cc=oxymoron@waste.org \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®