[lkml]   [2002]   [Feb]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: BK Kernel Hacking HOWTO
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,

> 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
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.


# A script to format BK changeset output in a manner that is easy to read.
# Andreas Dilger <> 13/02/2002


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";;

[ -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 <>
Alcove -
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:24    [W:0.089 / U:16.256 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site