cset #'s stable?

cset #'s stable?

[Frank Cusack]

Are changeset #'s stable?

I'm specifically looking at linux-2.5/net/sunrpc/clnt.c,
"rev 1.1153.63.[123]" which I recorded earlier as 1.1153.48.[123].

/fc

Re: cset #'s stable?

[Chris Wright]

* Frank Cusack (fcusack@fcusack.com) wrote:
> Are changeset #'s stable?
> 
> I'm specifically looking at linux-2.5/net/sunrpc/clnt.c,
> "rev 1.1153.63.[123]" which I recorded earlier as 1.1153.48.[123].

No, they are not.  The key, however, is stable (bk changes -k -r<rev>,
for example).

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

Re: cset #'s stable?

[Theodore Ts'o]

On Tue, Oct 21, 2003 at 09:52:09AM -0700, Chris Wright wrote:
> * Frank Cusack (fcusack@fcusack.com) wrote:
> > Are changeset #'s stable?
> > 
> > I'm specifically looking at linux-2.5/net/sunrpc/clnt.c,
> > "rev 1.1153.63.[123]" which I recorded earlier as 1.1153.48.[123].
> 
> No, they are not.  The key, however, is stable (bk changes -k -r<rev>,
> for example).

Changeset numbers are subject to change when you merge in other
changesets which depend on earlier changesets.  So older changeset
numbers tend to be more stable compared to newer changeset numbers,
and changeset numbers won't change unless you have done a pull (or
someone else has done a push) to your repository.

					- Ted

Re: cset #'s stable?

[David Woodhouse]

On Tue, 2003-10-21 at 09:52 -0700, Chris Wright wrote:
> * Frank Cusack (fcusack@fcusack.com) wrote:
> > Are changeset #'s stable?
> > 
> > I'm specifically looking at linux-2.5/net/sunrpc/clnt.c,
> > "rev 1.1153.63.[123]" which I recorded earlier as 1.1153.48.[123].
> 
> No, they are not.  The key, however, is stable (bk changes -k -r<rev>,
> for example).

This is in the X-BK-ChangeSetKey: header of the mails sent to the
mailing lists.

-- 
dwmw2

Re: cset #'s stable?

[Tom Rini]

On Tue, Oct 21, 2003 at 09:52:09AM -0700, Chris Wright wrote:
> * Frank Cusack (fcusack@fcusack.com) wrote:
> > Are changeset #'s stable?
> > 
> > I'm specifically looking at linux-2.5/net/sunrpc/clnt.c,
> > "rev 1.1153.63.[123]" which I recorded earlier as 1.1153.48.[123].
> 
> No, they are not.  The key, however, is stable (bk changes -k -r<rev>,
> for example).

FWIW, it's easy to go back and forth as well, bash (pure sh?) functions
to do it:
REVTOKEY() {
	if [ -z "$1" ]; then
		echo "Usage: REVTOKEY revision-number"
	else
		if [ ! -f ChangeSet -a ! -f SCCS/s.ChangeSet ]; then
			echo "Must be run from the base of a BitKeeper repositor
y"
		else
			echo -n "The key is: "
			bk prs -r$1 -hnd:KEY: ChangeSet
		fi
	fi
}

KEYTOREV() {
	if [ -z "$1" ]; then
		echo "Usage: KEYTOREV key"
	else
		if [ ! -f ChangeSet -a ! -f SCCS/s.ChangeSet ]; then
			echo "Must be run from the base of a BitKeeper repositor
y"
		else
			echo -n "The key is: "
			bk prs -r$1 -hnd:REV: ChangeSet
		fi
	fi
}

-- 
Tom Rini
http://gate.crashing.org/~trini/

Re: cset #'s stable?

[Chris Wright]

* 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 ;-)

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

Re: cset #'s stable?

[Larry McVoy]

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