From: Johannes Sixt <j.sixt@viscovery.net>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Sverre Rabbelier <srabbelier@gmail.com>,
Ramkumar Ramachandra <artagnon@gmail.com>,
Jonathan Nieder <jrnieder@gmail.com>, Jeff King <peff@peff.net>
Subject: Re: [PATCH] revert: add --stdin option to read commits from stdin
Date: Mon, 14 Jun 2010 08:20:43 +0200 [thread overview]
Message-ID: <4C15CA3B.3050908@viscovery.net> (raw)
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
prev parent reply other threads:[~2010-06-14 6:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 3:22 [PATCH] revert: add --stdin option to read commits from stdin Christian Couder
2010-06-14 5:20 ` Jonathan Nieder
2010-06-14 5:28 ` [PATCH 1/3] t3508 (cherry-pick): futureproof against unmerged files Jonathan Nieder
2010-06-14 5:29 ` [PATCH 2/3] revert: accept arbitrary rev-list options Jonathan Nieder
2010-06-14 5:32 ` [PATCH 3/3] revert: do not rebuild argv on heap Jonathan Nieder
2010-06-15 3:28 ` [PATCH] revert: add --stdin option to read commits from stdin Christian Couder
2010-06-14 6:20 ` 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=4C15CA3B.3050908@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=artagnon@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
--cc=srabbelier@gmail.com \
/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).