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

Re: [PATCH] revert: add --stdin option to read commits from stdin

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Jun 14, 2010, 06:20 UTC
Message-ID
<4C15CA3B.3050908@viscovery.net>
In-Reply-To
<20100614032251.20121.83253.chriscool@tuxfamily.org>
Am 6/14/2010 5:22, schrieb Christian Couder:
> +--stdin::
> +	In addition to the '<commit>' listed on the command
> +	line, read them from the standard input.
And the order in which --stdin and command line commits are processed is...?
-- Hannes
Previous: Christian Couder
Message 7 of 7 in “revert: add --stdin option to read commits from stdin”
  1. revert: add --stdin option to read commits from stdinChristian Couder, Jun 14, 2010
  2. Jonathan NiederJun 14, 2010
  3. 1/3 t3508 (cherry-pick): futureproof against unmerged filesJonathan Nieder, Jun 14, 2010
  4. 2/3 revert: accept arbitrary rev-list optionsJonathan Nieder, Jun 14, 2010
  5. 3/3 revert: do not rebuild argv on heapJonathan Nieder, Jun 14, 2010
  6. Christian CouderJun 15, 2010
  7. Johannes SixtJun 14, 2010

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.