From: Johannes Sixt <j.sixt@viscovery.net>
To: Josh Triplett <josh@joshtriplett.org>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] archive: Refuse to write the archive to a terminal.
Date: Thu, 17 Sep 2009 07:53:35 +0200 [thread overview]
Message-ID: <4AB1CEDF.7020105@viscovery.net> (raw)
In-Reply-To: <20090917014854.GD3274@feather>
Josh Triplett schrieb:
> On Wed, Sep 16, 2009 at 01:11:26PM +0200, Johannes Sixt wrote:
>> How about '--output -' instead?
>
> Yeah, that seems significantly better than --force. Though I don't
> particularly care for the '-' convention to mean 'stdout'; in principle
> that ought to create a file named '-' in the current directory.
> /dev/stdout makes more sense, and doesn't require any work on git's
> part beyond this patch.
Except that /dev/stdout is not portable. You can always say --output ./-
if you want an oddly named file in the current directory.
-- Hannes
prev parent reply other threads:[~2009-09-17 5:55 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
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 [this message]
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=4AB1CEDF.7020105@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).