Re: BK Kernel Hacking HOWTO

[Stelian Pop <stelian.pop@fr.alcove.com>]

On Thu, Feb 21, 2002 at 11:13:38AM -0500, Jeff Garzik wrote:

> Let's start with this progression:
> Each BitKeeper source tree on disk is a repository unto itself.
> Each repository has a parent.

except the official Linus one, http://linux.bkbits.net

> Submitting Changes to Linus

I would really like this section to be splitted in two:

- one for Linus' lieutenants:
	your explanation, with tree to pull from is ok.

- one for occasionnal contributors:
	either plain patch on l-k
		or
	plain patch + BK changeset on l-k (using the
	Andreas Dilger script wrapper maybe, see below)
	

> You can and should use the command "bk comment -C<rev>" to update the
> commit text, and improve it after the fact.

Or use bk revtool in X.

Stelian.

#!/bin/sh
# A script to format BK changeset output in a manner that is easy to read.
# Andreas Dilger <adilger@turbolabs.com>  13/02/2002

PROG=bksend

usage() {
	echo "usage: $PROG -r<rev>"
	echo -e "\twhere <rev> is of the form '1.23', '1.23..', '1.23..1.27',"
	echo -e "\tor '+' to indicate the most recent revision"

	exit 1
}

case $1 in
-r) REV=$2; shift ;;
-r*) REV=`echo $1 | sed 's/^-r//'` ;;
*) echo "$PROG: no revision given, you probably don't want that";;
esac

[ -z "$REV" ] && usage

bk changes -r$REV
bk export -tpatch -du -h -r$REV
echo -e "\n================================================================\n\n"
bk send -wgzip_uu -r$REV -

-- 
Stelian Pop <stelian.pop@fr.alcove.com>
Alcove - http://www.alcove.com