remove BK documentation
PATCH 1/1 remove BK documentation
There's no longer a reason to document the obsolete BK usage.
---
This patch was already sent on:
- 9 Apr 2005
Documentation/00-INDEX | 2 Documentation/BK-usage/00-INDEX | 51 --- Documentation/BK-usage/bk-kernel-howto.txt | 283 --------------------- Documentation/BK-usage/bk-make-sum | 34 -- Documentation/BK-usage/bksend | 36 -- Documentation/BK-usage/bz64wrap | 41 --- Documentation/BK-usage/cpcset | 36 -- Documentation/BK-usage/cset-to-linus | 49 --- Documentation/BK-usage/csets-to-patches | 44 --- Documentation/BK-usage/gcapatch | 8 Documentation/BK-usage/unbz64wrap | 25 - fs/cifs/README | 6 12 files changed, 3 insertions(+), 612 deletions(-)
Documentation/00-INDEX renamed from Documentation/00-INDEX.old +0 -2
@@ -12,8 +12,6 @@ 00-INDEX - this file. -BK-usage/ - - directory with info on BitKeeper. BUG-HUNTING - brute force method of doing binary search of patches to find bug. Changes
fs/cifs/README renamed from fs/cifs/README.old +3 -3
@@ -32,9 +32,9 @@ 6) make modules (or "make" if CIFS VFS not to be built as a module) For Linux 2.6: -1) Download the kernel (e.g. from http://www.kernel.org or from bitkeeper -at bk://linux.bkbits.net/linux-2.5) and change directory into the top -of the kernel directory tree (e.g. /usr/src/linux-2.5.73) +1) Download the kernel (e.g. from http://www.kernel.org +and change directory into the top of the kernel directory tree +(e.g. /usr/src/linux-2.5.73) 2) make menuconfig (or make xconfig) 3) select cifs from within the network filesystem choices 4) save and exit
Documentation/BK-usage/00-INDEX deleted +0 -51
51 lines not on this page · raw message
Documentation/BK-usage/bk-kernel-howto.txt deleted +0 -283
283 lines not on this page · raw message
Documentation/BK-usage/bk-make-sum deleted +0 -34
@@ -1,34 +0,0 @@ -#!/bin/sh -e -# DIR=$HOME/BK/axp-2.5 -# cd $DIR - -LINUS_REPO=$1 -DIRBASE=`basename $PWD` - -{ -cat <<EOT -Please do a - - bk pull bk://gkernel.bkbits.net/$DIRBASE - -This will update the following files: - -EOT - -bk export -tpatch -hdu -r`bk repogca $LINUS_REPO`,+ | diffstat -p1 2>/dev/null - -cat <<EOT - -through these ChangeSets: - -EOT - -bk changes -L -d'$unless(:MERGE:){ChangeSet|:CSETREV:\n}' $LINUS_REPO | -bk -R prs -h -d'$unless(:MERGE:){<:P:@:HOST:> (:D: :I:)\n$each(:C:){ (:C:)\n}\n}' - - -} > /tmp/linus.txt - -cat <<EOT -Mail text in /tmp/linus.txt; please check and send using your favourite -mailer. -EOT
Documentation/BK-usage/bksend deleted +0 -36
@@ -1,36 +0,0 @@ -#!/bin/sh -# A script to format BK changeset output in a manner that is easy to read. -# Andreas Dilger <[email protected]> 13/02/2002 -# -# Add diffstat output after Changelog <[email protected]> 21/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 - -echo "You can import this changeset into BK by piping this whole message to:" -echo "'| bk receive [path to repository]' or apply the patch as usual." - -SEP="\n===================================================================\n\n" -echo -e $SEP -env PAGER=/bin/cat bk changes -r$REV -echo -bk export -tpatch -du -h -r$REV | diffstat -echo; echo -bk export -tpatch -du -h -r$REV -echo -e $SEP -bk send -wgzip_uu -r$REV -
Documentation/BK-usage/bz64wrap deleted +0 -41
41 lines not on this page · raw message
Documentation/BK-usage/cpcset deleted +0 -36
@@ -1,36 +0,0 @@ -#!/bin/sh -# -# Purpose: Copy changeset patch and description from one -# repository to another, unrelated one. -# -# usage: cpcset [revision] [from-repository] [to-repository] -# - -REV=$1 -FROM=$2 -TO=$3 -TMPF=/tmp/cpcset.$$ - -rm -f $TMPF* - -CWD_SAVE=`pwd` -cd $FROM -bk changes -r$REV | \ - grep -v '^ChangeSet' | \ - sed -e 's/^ //g' > $TMPF.log - -USERHOST=`bk changes -r$REV | grep '^ChangeSet' | awk '{print $4}'` -export BK_USER=`echo $USERHOST | awk '-F@' '{print $1}'` -export BK_HOST=`echo $USERHOST | awk '-F@' '{print $2}'` - -bk export -tpatch -hdu -r$REV > $TMPF.patch && \ -cd $CWD_SAVE && \ -cd $TO && \ -bk import -tpatch -CFR -y"`cat $TMPF.log`" $TMPF.patch . && \ -bk commit -y"`cat $TMPF.log`" - -rm -f $TMPF* - -echo changeset $REV copied. -echo "" -
Documentation/BK-usage/csets-to-patches deleted +0 -44
44 lines not on this page · raw message
Documentation/BK-usage/cset-to-linus deleted +0 -49
49 lines not on this page · raw message
Documentation/BK-usage/gcapatch deleted +0 -8
@@ -1,8 +0,0 @@ -#!/bin/sh -# -# Purpose: Generate GNU diff of local changes versus canonical top-of-tree -# -# Usage: gcapatch > foo.patch -# - -bk export -tpatch -hdu -r`bk repogca bk://linux.bkbits.net/linux-2.5`,+
Documentation/BK-usage/unbz64wrap deleted +0 -25
@@ -1,25 +0,0 @@ -#!/bin/sh - -# unbz64wrap - the receiving side of a bzip2 | base64 stream -# Andreas Dilger <[email protected]> Jan 2002 - -# Sadly, mimencode does not appear to have good "begin" and "end" markers -# like uuencode does, and it is picky about getting the right start/end of -# the base64 stream, so we handle this explicitly here. - -PATH=$PATH:/usr/bin:/usr/local/bin:/usr/freeware/bin - -if mimencode -u < /dev/null > /dev/null 2>&1 ; then - SHOW= - while read LINE; do - case $LINE in - begin-base64*) SHOW=YES ;; - ====) SHOW= ;; - *) [ "$SHOW" ] && echo "$LINE" ;; - esac - done | mimencode -u | bunzip2 - exit $? -else - cat - | uudecode -o /dev/stdout | bunzip2 - exit $? -fi
Quoted 3 lines · Adrian Bunk
There's no longer a reason to document the obsolete BK usage.
Signed-off-by Adrian Bunk <[email protected]>
If you are going to remove some documents, please at least have the common courtesy of CC'ing the author of the documents.
Speaking as the author of 90% of Documentation/BK-usage directory, I ACK this patch.
Jeff
fs/cifs/README line 37
Quoted 12 lines · Adrian Bunk
fs/cifs/README renamed from fs/cifs/README.old +3
-3@@ -32,9 +32,9 @@ 6) make modules (or "make" if CIFS VFS not to be built as a module) For Linux 2.6: -1) Download the kernel (e.g. from http://www.kernel.org or from bitkeeper -at bk://linux.bkbits.net/linux-2.5) and change directory into the top -of the kernel directory tree (e.g. /usr/src/linux-2.5.73) +1) Download the kernel (e.g. from http://www.kernel.org +and change directory into the top of the kernel directory tree +(e.g. /usr/src/linux-2.5.73)
That lacks a closing paren now.
Andreas.
Signature · 4 lines
Andreas Schwab, SuSE Labs, [email protected] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
PATCH 1/1 remove BK documentation
Quoted 7 lines · Andreas Schwab
Quoted 5 lines · Adrian Bunk
fs/cifs/README renamed from fs/cifs/README.old +0
-0@@ -32,9 +32,9 @@ 6) make modules (or "make" if CIFS VFS not to be built as a module)
Quoted 9 lines
fs/cifs/README line 37
Quoted 7 lines
fs/cifs/README renamed from fs/cifs/README.old +3
-3For Linux 2.6: -1) Download the kernel (e.g. from http://www.kernel.org or from bitkeeper -at bk://linux.bkbits.net/linux-2.5) and change directory into the top -of the kernel directory tree (e.g. /usr/src/linux-2.5.73) +1) Download the kernel (e.g. from http://www.kernel.org +and change directory into the top of the kernel directory tree +(e.g. /usr/src/linux-2.5.73)That lacks a closing paren now.
Corrected patch below.
Quoted 1 line
Andreas.
cu
Adrian
<-- snip -->
There's no longer a reason to document the obsolete BK usage.
---
Documentation/00-INDEX | 2 Documentation/BK-usage/00-INDEX | 51 --- Documentation/BK-usage/bk-kernel-howto.txt | 283 --------------------- Documentation/BK-usage/bk-make-sum | 34 -- Documentation/BK-usage/bksend | 36 -- Documentation/BK-usage/bz64wrap | 41 --- Documentation/BK-usage/cpcset | 36 -- Documentation/BK-usage/cset-to-linus | 49 --- Documentation/BK-usage/csets-to-patches | 44 --- Documentation/BK-usage/gcapatch | 8 Documentation/BK-usage/unbz64wrap | 25 - fs/cifs/README | 6 12 files changed, 3 insertions(+), 612 deletions(-)
Documentation/00-INDEX renamed from Documentation/00-INDEX.old +0 -2
@@ -12,8 +12,6 @@ 00-INDEX - this file. -BK-usage/ - - directory with info on BitKeeper. BUG-HUNTING - brute force method of doing binary search of patches to find bug. Changes
fs/cifs/README renamed from fs/cifs/README.old +3 -3
@@ -32,9 +32,9 @@ 6) make modules (or "make" if CIFS VFS not to be built as a module) For Linux 2.6: -1) Download the kernel (e.g. from http://www.kernel.org or from bitkeeper -at bk://linux.bkbits.net/linux-2.5) and change directory into the top -of the kernel directory tree (e.g. /usr/src/linux-2.5.73) +1) Download the kernel (e.g. from http://www.kernel.org) +and change directory into the top of the kernel directory tree +(e.g. /usr/src/linux-2.5.73) 2) make menuconfig (or make xconfig) 3) select cifs from within the network filesystem choices 4) save and exit
Documentation/BK-usage/00-INDEX deleted +0 -51
51 lines not on this page · raw message
Documentation/BK-usage/bk-kernel-howto.txt deleted +0 -283
283 lines not on this page · raw message
Documentation/BK-usage/bk-make-sum deleted +0 -34
@@ -1,34 +0,0 @@ -#!/bin/sh -e -# DIR=$HOME/BK/axp-2.5 -# cd $DIR - -LINUS_REPO=$1 -DIRBASE=`basename $PWD` - -{ -cat <<EOT -Please do a - - bk pull bk://gkernel.bkbits.net/$DIRBASE - -This will update the following files: - -EOT - -bk export -tpatch -hdu -r`bk repogca $LINUS_REPO`,+ | diffstat -p1 2>/dev/null - -cat <<EOT - -through these ChangeSets: - -EOT - -bk changes -L -d'$unless(:MERGE:){ChangeSet|:CSETREV:\n}' $LINUS_REPO | -bk -R prs -h -d'$unless(:MERGE:){<:P:@:HOST:> (:D: :I:)\n$each(:C:){ (:C:)\n}\n}' - - -} > /tmp/linus.txt - -cat <<EOT -Mail text in /tmp/linus.txt; please check and send using your favourite -mailer. -EOT
Documentation/BK-usage/bksend deleted +0 -36
@@ -1,36 +0,0 @@ -#!/bin/sh -# A script to format BK changeset output in a manner that is easy to read. -# Andreas Dilger <[email protected]> 13/02/2002 -# -# Add diffstat output after Changelog <[email protected]> 21/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 - -echo "You can import this changeset into BK by piping this whole message to:" -echo "'| bk receive [path to repository]' or apply the patch as usual." - -SEP="\n===================================================================\n\n" -echo -e $SEP -env PAGER=/bin/cat bk changes -r$REV -echo -bk export -tpatch -du -h -r$REV | diffstat -echo; echo -bk export -tpatch -du -h -r$REV -echo -e $SEP -bk send -wgzip_uu -r$REV -
Documentation/BK-usage/bz64wrap deleted +0 -41
41 lines not on this page · raw message
Documentation/BK-usage/cpcset deleted +0 -36
@@ -1,36 +0,0 @@ -#!/bin/sh -# -# Purpose: Copy changeset patch and description from one -# repository to another, unrelated one. -# -# usage: cpcset [revision] [from-repository] [to-repository] -# - -REV=$1 -FROM=$2 -TO=$3 -TMPF=/tmp/cpcset.$$ - -rm -f $TMPF* - -CWD_SAVE=`pwd` -cd $FROM -bk changes -r$REV | \ - grep -v '^ChangeSet' | \ - sed -e 's/^ //g' > $TMPF.log - -USERHOST=`bk changes -r$REV | grep '^ChangeSet' | awk '{print $4}'` -export BK_USER=`echo $USERHOST | awk '-F@' '{print $1}'` -export BK_HOST=`echo $USERHOST | awk '-F@' '{print $2}'` - -bk export -tpatch -hdu -r$REV > $TMPF.patch && \ -cd $CWD_SAVE && \ -cd $TO && \ -bk import -tpatch -CFR -y"`cat $TMPF.log`" $TMPF.patch . && \ -bk commit -y"`cat $TMPF.log`" - -rm -f $TMPF* - -echo changeset $REV copied. -echo "" -
Documentation/BK-usage/csets-to-patches deleted +0 -44
44 lines not on this page · raw message
Documentation/BK-usage/cset-to-linus deleted +0 -49
49 lines not on this page · raw message
Documentation/BK-usage/gcapatch deleted +0 -8
@@ -1,8 +0,0 @@ -#!/bin/sh -# -# Purpose: Generate GNU diff of local changes versus canonical top-of-tree -# -# Usage: gcapatch > foo.patch -# - -bk export -tpatch -hdu -r`bk repogca bk://linux.bkbits.net/linux-2.5`,+
Documentation/BK-usage/unbz64wrap deleted +0 -25
@@ -1,25 +0,0 @@ -#!/bin/sh - -# unbz64wrap - the receiving side of a bzip2 | base64 stream -# Andreas Dilger <[email protected]> Jan 2002 - -# Sadly, mimencode does not appear to have good "begin" and "end" markers -# like uuencode does, and it is picky about getting the right start/end of -# the base64 stream, so we handle this explicitly here. - -PATH=$PATH:/usr/bin:/usr/local/bin:/usr/freeware/bin - -if mimencode -u < /dev/null > /dev/null 2>&1 ; then - SHOW= - while read LINE; do - case $LINE in - begin-base64*) SHOW=YES ;; - ====) SHOW= ;; - *) [ "$SHOW" ] && echo "$LINE" ;; - esac - done | mimencode -u | bunzip2 - exit $? -else - cat - | uudecode -o /dev/stdout | bunzip2 - exit $? -fi
Quoted 7 lines · Jeff Garzik
Quoted 3 lines · Adrian Bunk
There's no longer a reason to document the obsolete BK usage.
Signed-off-by Adrian Bunk <[email protected]>If you are going to remove some documents, please at least have the common courtesy of CC'ing the author of the documents.
I'd have done this if you were listed as author in any of the files.
Quoted 4 lines
Speaking as the author of 90% of
Documentation/BK-usagedirectory, I ACK this patch.Jeff
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 6 lines · Adrian Bunk
Quoted 4 lines · Jeff Garzik
Quoted 2 lines · Adrian Bunk
There's no longer a reason to document the obsolete BK usage.
Quoted 7 lines
Quoted 4 lines
Quoted 1 line
Signed-off-by Adrian Bunk <[email protected]>If you are going to remove some documents, please at least have the common courtesy of CC'ing the author of the documents.
I'd have done this if you were listed as author in any of the files.
Look at the changelog or file revision history...
Files you wish to remove were obviously written by -somebody-. When removing things, make a serious effort to contact the author.
Jeff
Quoted 5 lines · Jeff Garzik
Quoted 1 line · Adrian Bunk
I'd have done this if you were listed as author in any of the files.
Look at the changelog or file revision history...
The few times I've submitted patches I've been lucky and MAINTAINERS pointed the cc: in the right direction(s) (or at least close enough).
It might be useful to document, for somebody who has just a Linus -rc or an Andrew -mm kernel source tree, what magic incantations need to be done to query the changelog or file revision history for that sort of info. Pulling multiple release Changelogs from www.kernel.org and doing a binary search isn't the most fun thing in the world (especially because sometimes the Changelog entry just says "add documentation about Foo" so a search for Documentation/foo.txt misses...)
Quoted 7 lines · Jeff Garzik
Quoted 3 lines · Adrian Bunk
There's no longer a reason to document the obsolete BK usage.
Signed-off-by Adrian Bunk <[email protected]>
Quoted 7 lines
If you are going to remove some documents, please at least have the common courtesy of CC'ing the author of the documents.
Speaking as the author of 90% of
Documentation/BK-usagedirectory, I ACK this patch.Jeff
This seems like a good place to thank Adrian for his cleaning fetish, which makes the kernel code and docs far less confusing, and Jeff, who put in most of the effort in documenting bk.
Documentation authors really should mention themselves in the introduction, docs aren't sexy and don't get your name in the news, but they are a vital part of making Linux usable.
Signature · 3 lines
-bill davidsen ([email protected]) "The secret to procrastination is to put things off until the last possible moment - but no longer" -me
Uttered Bill Davidsen <[email protected]>, spake thus:
Quoted 3 lines
Documentation authors really should mention themselves in the introduction, docs aren't sexy and don't get your name in the news, but they are a vital part of making Linux usable.
If you'd like to volunteer for the Fedora Documentation Project over at
we may be able to overcome the rest the shortcomings you mentioned ;-)