From: Larry McVoy <lm@bitmover.com>
To: Paul Larson <plars@austin.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>, scott.feldman@intel.com
Subject: Re: LTP Nightly BK Test Failure
Date: Wed, 28 Aug 2002 08:10:36 -0700 [thread overview]
Message-ID: <20020828081036.B28927@work.bitmover.com> (raw)
In-Reply-To: <1030545604.2601.3.camel@plars.austin.ibm.com>; from plars@austin.ibm.com on Wed, Aug 28, 2002 at 09:40:03AM -0500
On Wed, Aug 28, 2002 at 09:40:03AM -0500, Paul Larson wrote:
> This bk tree covered up to cset 1.523.1.3 and there were several e100
Because revisions in BK change if there is parallel development, it's
far more effective if you list a changeset as either
bk changes -r1.523.1.3
i.e.,
ChangeSet@1.523.1.3, 2002-08-27 18:29:55-07:00, fdavis@si.rr.com
[PATCH] drivers/media/video/bt819.c
Here's the bt819 i2c-old --> i2c patch.
or as the revision and the key,
bk prs -hr1.523.1.3 -nd':I: (:KEY:)'
i.e.,
1.523.1.3 (fdavis@si.rr.com|ChangeSet|20020828012955|42356)
You can use the key any place you can use the revision, like so
bk changes -r'fdavis@si.rr.com|ChangeSet|20020828012955|42356'
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2002-08-28 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 14:40 Paul Larson
2002-08-28 15:10 ` Larry McVoy [this message]
2002-08-28 15:28 ` Paul Larson
2002-09-06 5:55 Matthias Urlichs
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=20020828081036.B28927@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linux-kernel@vger.kernel.org \
--cc=plars@austin.ibm.com \
--cc=scott.feldman@intel.com \
/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®