From: Larry McVoy <lm@bitmover.com>
To: Chris Wright <chrisw@osdl.org>
Cc: Tom Rini <trini@kernel.crashing.org>,
Frank Cusack <fcusack@fcusack.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: cset #'s stable?
Date: Fri, 24 Oct 2003 16:34:17 -0700 [thread overview]
Message-ID: <20031024233417.GA12636@work.bitmover.com> (raw)
In-Reply-To: <20031024153907.D19313@osdlab.pdx.osdl.net>
On Fri, Oct 24, 2003 at 03:39:07PM -0700, Chris Wright wrote:
> * Tom Rini (trini@kernel.crashing.org) wrote:
> > FWIW, it's easy to go back and forth as well, bash (pure sh?) functions
> > to do it:
>
> <snipped useful shell funcs>
>
> Nice. I believe current bk lets you do bk changes -k -r<rev> to get key
> from ChangeSet file (identical to bk prs -r -hnd:Key ChangeSet), and
> echo key | bk key2rev ChangeSet to convert back. Not much simpler, but
> a little ;-)
In general, we're moving towards a BK version where keys (internal revisions,
sort of like mail message id's) are useable anywhere a rev is useable.
One place we'll be using this is on BK/Web so that you guys can have
URLs that don't change out from underneath you.
We should fix that at the same time that we turn on the GNU patch server
so you can get any changeset as a patch. The dual T1's are due in at the
end of this month.
There may be some delay, I'm away dealing with family stuff that is way
higher in priority than this but I'll try and get someone else to do it
if it takes longer than the end of the month before I'm back.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
prev parent reply other threads:[~2003-10-24 23:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 16:13 cset #'s stable? Frank Cusack
2003-10-21 16:52 ` Chris Wright
2003-10-21 17:23 ` Theodore Ts'o
2003-10-22 12:40 ` David Woodhouse
2003-10-24 22:20 ` Tom Rini
2003-10-24 22:39 ` Chris Wright
2003-10-24 23:34 ` Larry McVoy [this message]
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=20031024233417.GA12636@work.bitmover.com \
--to=lm@bitmover.com \
--cc=chrisw@osdl.org \
--cc=fcusack@fcusack.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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.