From: Chris Wright <chrisw@osdl.org>
To: Zack Brown <zbrown@tumblerings.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: matching "Cset exclude" changelog entries to the changelog entries they revert.
Date: Tue, 20 Apr 2004 17:26:22 -0700 [thread overview]
Message-ID: <20040420172622.K22989@build.pdx.osdl.net> (raw)
In-Reply-To: <20040421001236.GA16901@tumblerings.org>; from zbrown@tumblerings.org on Tue, Apr 20, 2004 at 05:12:36PM -0700
* Zack Brown (zbrown@tumblerings.org) wrote:
> for instance, "Cset exclude: davej@suse.de|ChangeSet|20020403195622" is in
> 2.5.8-pre2, as the full text of the changelog entry.
bk prs -r"davej@suse.de|ChangeSet|20020403195622" -hnd:REV: ChangeSet
That will give you the rev from that key in the Cset exclude message.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2004-04-21 0:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 0:12 matching "Cset exclude" changelog entries to the changelog entries they revert Zack Brown
2004-04-21 0:26 ` Chris Wright [this message]
2004-04-21 0:38 ` Zack Brown
2004-04-21 0:41 ` Chris Wright
2004-04-21 1:02 ` Andy Isaacson
2004-04-21 1:29 ` Zack Brown
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=20040420172622.K22989@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zbrown@tumblerings.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