From: "Matthias Urlichs" <smurf@smurf.noris.de>
To: linux-kernel@vger.kernel.org
Subject: [2.6 patch] bksend example script fix
Date: Fri, 18 Feb 2005 10:28:42 +0100 [thread overview]
Message-ID: <20050218092842.GA12309@kiste> (raw)
[-- Attachment #1: Type: text/plain, Size: 791 bytes --]
The "bksend" example script doesn't work if PAGER (used by "bk changes")
is set to something which doesn't fallback to plain stdout if its output
isn't a tty.
Fixed by forcing PAGER to be /bin/cat.
Signed-Off-By: Matthias Urlichs <smurf@debian.org>
diff -Nru a/Documentation/BK-usage/bksend b/Documentation/BK-usage/bksend
--- a/Documentation/BK-usage/bksend 2005-02-18 10:06:04 +01:00
+++ b/Documentation/BK-usage/bksend 2005-02-18 10:06:04 +01:00
@@ -27,7 +27,7 @@
SEP="\n===================================================================\n\n"
echo -e $SEP
-bk changes -r$REV
+env PAGER=/bin/cat bk changes -r$REV
echo
bk export -tpatch -du -h -r$REV | diffstat
echo; echo
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | smurf@smurf.noris.de
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2005-02-18 9:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050218092842.GA12309@kiste \
--to=smurf@smurf.noris.de \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).