git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Tan <pyokagan@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>,
	Johannes Schindelin <johannes.schindelin@gmx.de>,
	Stefan Beller <sbeller@google.com>,
	Chris Packham <judge.packham@gmail.com>
Subject: Re: [PATCH 2/5] am: teach StGit patch parser how to read from stdin
Date: Tue, 9 Jun 2015 17:38:25 +0800	[thread overview]
Message-ID: <CACRoPnTAOsJE_VWJCadHh6Hpcw_c9DK7qARA5kC8_BBoXWHH6A@mail.gmail.com> (raw)
In-Reply-To: <xmqqh9qi9dmh.fsf@gitster.dls.corp.google.com>

On Tue, Jun 9, 2015 at 3:57 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Paul Tan <pyokagan@gmail.com> writes:
>
>> git-mailsplit, which splits mbox patches, will read the patch from stdin
>> when the filename is "-" or there are no files listed on the
>> command-line.
>>
>> To be consistent with this behavior, teach the StGit patch parser to
>> read from stdin if the filename is "-" or no files are listed on the
>> command-line.
>
> Hmm, doesn't
>
>         perl -ne 'processing for each line'
>
> with or without a BEGIN {} block, read from the standard input (if
> no filename is given) or the given file (if given), and more
> importantly, doesn't it treat a lone "-" as STDIN anyway?
>
> That is, wouldn't it make more sense to do something like:
>
>         test $# != 0 || set -- -
>         for stgit
>         do
>                 ...
>                 @@PERL@@ -ne 'BEGIN { $subject = 0 }
>                         ...
>                 ' "$stgit" >"$dotest/$msgnum" || clean_abort
>         done
>
> Same for patch 5/5.

Ah yes, this makes more sense.

Thanks,
Paul

  reply	other threads:[~2015-06-09  9:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-08 15:48 [PATCH 0/5] am: improve test coverage and touch up foreign patch parsing Paul Tan
2015-06-08 15:48 ` [PATCH 1/5] t4150: test applying StGit patch Paul Tan
2015-06-08 15:48 ` [PATCH 2/5] am: teach StGit patch parser how to read from stdin Paul Tan
2015-06-08 19:57   ` Junio C Hamano
2015-06-09  9:38     ` Paul Tan [this message]
2015-06-08 15:48 ` [PATCH 3/5] t4150: test applying StGit series Paul Tan
2015-06-08 15:48 ` [PATCH 4/5] am: use gmtime() to parse mercurial patch date Paul Tan
2015-06-08 15:48 ` [PATCH 5/5] am: teach mercurial patch parser how to read from stdin Paul Tan
2015-06-08 17:13   ` Stefan Beller

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=CACRoPnTAOsJE_VWJCadHh6Hpcw_c9DK7qARA5kC8_BBoXWHH6A@mail.gmail.com \
    --to=pyokagan@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=johannes.schindelin@gmx.de \
    --cc=judge.packham@gmail.com \
    --cc=sbeller@google.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).