From: Larry McVoy <lm@bitmover.com>
To: Larry McVoy <lm@bitmover.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BK prob] - bogus cset
Date: Tue, 10 Dec 2002 17:42:53 -0800 [thread overview]
Message-ID: <20021210174253.A29772@work.bitmover.com> (raw)
In-Reply-To: <200212110140.gBB1e1o30094@work.bitmover.com>; from lm@bitmover.com on Tue, Dec 10, 2002 at 05:40:01PM -0800
By the way, the set of people who need to clean up are:
agoddard
aliz
andersg
anton
chrisl
cloos
frival
fsirl
peterc
purna
riel
rp
steve
vonbrand
according to the logs.
On Tue, Dec 10, 2002 at 05:40:01PM -0800, Larry McVoy wrote:
> I'm an idiot, in the process of optimizing the logging code (so you modem
> users send less data, a big deal in Europe), I put a test cset into the
> main tree at bk://linux.bkbits.net/linux-2.5 and a pile of people pulled
> it.
>
> Could you please do this:
>
> bk findkey 'lm@work.bitmover.com|ChangeSet|20021211000341|36093' ChangeSet
>
> If that returns nothing, you're fine. If it tells you a revision, then
> if that is the most recent revision, just do a
>
> bk undo -fr`bk findkey 'lm@work.bitmover.com|ChangeSet|20021211000341|36093' ChangeSet`
>
> and you're all set. If that isn't the most recent revision, i.e., you merged
> against that, send me an email and I'll straighten out the tree.
>
> Sorry about this, it won't happen again.
>
> --lm
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2002-12-11 1:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 1:40 [BK prob] - bogus cset Larry McVoy
2002-12-11 1:42 ` Larry McVoy [this message]
2002-12-10 21:28 ` Alex Goddard
2002-12-11 1:49 ` Larry McVoy
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=20021210174253.A29772@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.