From: Karim Yaghmour <karim@opersys.com>
To: Christian Hesse <mail@earthworm.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Kernel .patches support
Date: Thu, 23 Jun 2005 18:38:34 -0400 [thread overview]
Message-ID: <42BB39EA.5080109@opersys.com> (raw)
In-Reply-To: <200506232358.34897.mail@earthworm.de>
Christian Hesse wrote:
> every time I apply a patch to my kernel tree I (or my scripts) make an
>
> echo $PATCHNAME $PATCHVERSION >> .patches
>
> This patch makes the file accessible via /proc/patches.gz. I think this can be
> handy if you want to know what patches you (or your distributor) applied to
> your running kernel...
I haven't looked at the implementation, but I love the functionality.
Karim
--
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 1-866-677-4546
next prev parent reply other threads:[~2005-06-23 22:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 21:58 [PATCH] Kernel .patches support Christian Hesse
2005-06-23 22:38 ` Karim Yaghmour [this message]
2005-06-24 6:02 ` Ian Campbell
2005-06-24 7:36 ` Adrian Bunk
2005-06-24 8:57 ` Coywolf Qi Hunt
2005-06-24 20:48 ` Christian Hesse
2005-06-24 21:03 ` Christian Hesse
2005-06-24 22:31 ` Adrian Bunk
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=42BB39EA.5080109@opersys.com \
--to=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@earthworm.de \
/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