From: Paul Larson <plars@austin.ibm.com>
To: Larry McVoy <lm@bitmover.com>
Cc: lkml <linux-kernel@vger.kernel.org>, scott.feldman@intel.com
Subject: Re: LTP Nightly BK Test Failure
Date: 28 Aug 2002 10:28:30 -0500 [thread overview]
Message-ID: <1030548511.2602.8.camel@plars.austin.ibm.com> (raw)
In-Reply-To: <20020828081036.B28927@work.bitmover.com>
On Wed, 2002-08-28 at 10:10, Larry McVoy wrote:
> 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
...
I didn't think about that, thanks for the tip. I'll make sure to do it
like that in future reports. Of course if there's any confusion, the
cset numbers I've been giving can be looked up on the linux-2.5 tree at
bkbits since I test against an unmodified pull from that tree.
Thanks,
Paul Larson
next prev parent reply other threads:[~2002-08-28 15:34 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
2002-08-28 15:28 ` Paul Larson [this message]
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=1030548511.2602.8.camel@plars.austin.ibm.com \
--to=plars@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.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®