From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git <git@vger.kernel.org>
Subject: Re: [BUG] [PATCH]: run-command.c
Date: Fri, 21 Oct 2016 10:19:07 -0700 [thread overview]
Message-ID: <xmqq37jpd3hw.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20161021090029.glr5u6gwrxluavir@sigill.intra.peff.net> (Jeff King's message of "Fri, 21 Oct 2016 05:00:29 -0400")
Jeff King <peff@peff.net> writes:
>> 16:42:45$ cat /proc/2601/cmdline | xargs -0 -n1 echo
>> /bin/sh
>> -c
>> echo $PWD;sleep 600
>> echo $PWD;sleep 600
>
> This duplicated argument is expected and normal.
Well explained. Thanks.
prev parent reply other threads:[~2016-10-21 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 5:50 [BUG] [PATCH]: run-command.c Duncan Roe
2016-10-21 9:00 ` Jeff King
2016-10-21 11:07 ` Duncan Roe
2016-10-21 17:19 ` Junio C Hamano [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=xmqq37jpd3hw.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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