From: Mikael Magnusson <mikachu@gmail.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Josh Triplett <josh@joshtriplett.org>,
git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] archive: Refuse to write the archive to a terminal.
Date: Wed, 16 Sep 2009 13:27:13 +0200 [thread overview]
Message-ID: <237967ef0909160427m4d7de120tf5ef3176f75123ad@mail.gmail.com> (raw)
In-Reply-To: <4AB0C7DE.7030109@viscovery.net>
2009/9/16 Johannes Sixt <j.sixt@viscovery.net>:
> Josh Triplett schrieb:
>> I considered adding a -f/--force option, like gzip has, but writing an
>> archive to a tty seems like a sufficiently insane use case that I'll let
>> whoever actually needs that write the patch for it. ;)
>
> How about '--output -' instead?
You could always just add '|cat'.
--
Mikael Magnusson
next prev parent reply other threads:[~2009-09-16 11:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 10:31 [PATCH] archive: Refuse to write the archive to a terminal Josh Triplett
2009-09-16 11:11 ` Johannes Sixt
2009-09-16 11:27 ` Mikael Magnusson [this message]
2009-09-16 11:48 ` Reece Dunn
2009-09-16 12:57 ` Matthieu Moy
2009-09-17 1:49 ` Josh Triplett
2009-09-17 5:53 ` Johannes Sixt
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=237967ef0909160427m4d7de120tf5ef3176f75123ad@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=josh@joshtriplett.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).