From: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Git Mailing List <git@vger.kernel.org>, Petr Baudis <pasky@ucw.cz>
Subject: Re: How to get bash to shut up about SIGPIPE?
Date: Thu, 28 Apr 2005 21:03:21 +0200 [thread overview]
Message-ID: <42713379.7080107@lsrfire.ath.cx> (raw)
In-Reply-To: <Pine.LNX.4.58.0504281121430.18901@ppc970.osdl.org>
Linus Torvalds schrieb:
> Right now my major gripe with cogito is "cg-log" (which is actually
> the only command I use right now, everything else I just do by hand
> with the raw git archive) is that bash is being an ass about SIGPIPE,
> and when I only look at the top part of the log, ie I do something
> like:
>
> torvalds@ppc970:~/src/cogito> git log | head
I think you misspelled "cg-log". :-D
Doing "cg-log | head" gives me 10 lines of log and nothing else. Maybe
the problem has been fixed between 0.7 and the current version I'm using
(commit ID 49612c471eebd26efe926a71752e254c1cdc382d)?
Rene
next prev parent reply other threads:[~2005-04-28 18:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 18:28 How to get bash to shut up about SIGPIPE? Linus Torvalds
2005-04-28 19:03 ` Rene Scharfe [this message]
2005-04-28 19:21 ` Linus Torvalds
2005-04-28 20:13 ` Rene Scharfe
2005-04-28 20:27 ` Ryan Anderson
2005-04-28 20:47 ` Linus Torvalds
2005-05-01 12:07 ` Herbert Xu
2005-05-01 15:51 ` David A. Wheeler
2005-05-02 16:10 ` Paul Jackson
2005-05-04 2:30 ` David A. Wheeler
2005-05-04 2:50 ` Linus Torvalds
2005-05-04 8:26 ` Herbert Xu
2005-04-28 21:31 ` Edgar Toernig
2005-04-28 22:16 ` Linus Torvalds
2005-04-29 1:00 ` Joshua T. Corbin
2005-04-30 0:22 ` Paul Jackson
2005-04-30 2:59 ` Linus Torvalds
2005-04-30 6:29 ` Paul Jackson
2005-04-30 11:04 ` Rene Scharfe
2005-05-02 22:17 ` Paul Jackson
2005-05-02 23:17 ` Petr Baudis
2005-05-03 1:44 ` Paul Jackson
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=42713379.7080107@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
--cc=torvalds@osdl.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).