From: Andy Isaacson <adi@bitmover.com>
To: Chris Wright <chrisw@osdl.org>, 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 18:02:26 -0700 [thread overview]
Message-ID: <20040421010226.GC27313@bitmover.com> (raw)
In-Reply-To: <20040420174147.G21045@build.pdx.osdl.net> <20040421003820.GB16901@tumblerings.org> <20040420172622.K22989@build.pdx.osdl.net>
On Tue, Apr 20, 2004 at 05:26:22PM -0700, Chris Wright wrote:
> * 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.
You can use cset keys just about anywhere you can use revision numbers
in the BK interface. So,
% bk changes -r'davej@suse.de|ChangeSet|20020403195622'
does the right thing.
On Tue, Apr 20, 2004 at 05:38:20PM -0700, Zack Brown wrote:
> Will this give me the text of the changelog entry being reverted? That's
> what I need to find.
The "changes" command I give above will.
I'll see if I can get the "cset exclude" text to be an HREF. In the
meantime, you can construct a working URL by appending the cset key to
http://linux.bkbits.net:8080/linux-2.5/cset@
like so:
http://linux.bkbits.net:8080/linux-2.5/cset@davej@suse.de|ChangeSet|20020403195622
-andy
next prev parent reply other threads:[~2004-04-21 1:02 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
2004-04-21 0:38 ` Zack Brown
2004-04-21 0:41 ` Chris Wright
2004-04-21 1:02 ` Andy Isaacson [this message]
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=20040421010226.GC27313@bitmover.com \
--to=adi@bitmover.com \
--cc=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