git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] archive: Refuse to write the archive to a terminal.

From
Josh Triplett <josh@joshtriplett.org>
Date
Sep 17, 2009, 01:49 UTC
Message-ID
<20090917014854.GD3274@feather>
In-Reply-To
<4AB0C7DE.7030109@viscovery.net>
On Wed, Sep 16, 2009 at 01:11:26PM +0200, Johannes Sixt wrote:
Show 6 quoted lines
> 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?

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.

- Josh Triplett
Previous: Matthieu MoyNext: Johannes Sixt
Message 6 of 7 in “archive: Refuse to write the archive to a terminal.”
  1. archive: Refuse to write the archive to a terminal.Josh Triplett, Sep 16, 2009
  2. Johannes SixtSep 16, 2009
  3. Mikael MagnussonSep 16, 2009
  4. Reece DunnSep 16, 2009
  5. Matthieu MoySep 16, 2009
  6. Josh TriplettSep 17, 2009
  7. Johannes SixtSep 17, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.