All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Olivier ROLAND <cyrus-dev@edla.org>, git@vger.kernel.org
Subject: Re: Bug report : bad filter-branch (OSX only)
Date: Wed, 29 Apr 2015 10:13:06 -0700	[thread overview]
Message-ID: <xmqqegn26eot.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20150429164315.GA26682@peff.net> (Jeff King's message of "Wed, 29 Apr 2015 12:43:15 -0400")

Jeff King <peff@peff.net> writes:

> ... would behave incorrectly without "-r". I would be shocked if that ever
> happens in real life, but I think it doesn't hurt to be careful.

Ahh, OK.  I overlooked the continued-line possibility.

> $$ is always the pid of the main shell process,...

Thanks for straightening me out---I was too lazy to run strace ;-)

> ... But I can imagine a shell that is smart
> enough to realize a fork is not required in this instance.

Yup.  I think that is a natural thing to optimize for implementors
of shells.

Thanks.

  reply	other threads:[~2015-04-29 17:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-26  9:25 Bug report : bad filter-branch (OSX only) Olivier ROLAND
2015-04-28  5:55 ` Jeff King
2015-04-28 11:02   ` Olivier ROLAND
2015-04-29  4:39     ` Jeff King
2015-04-29  4:56       ` Jeff King
2015-04-29  5:39         ` Junio C Hamano
2015-04-29 15:48           ` Jeff King
2015-04-29 16:30             ` Junio C Hamano
2015-04-29 16:43               ` Jeff King
2015-04-29 17:13                 ` Junio C Hamano [this message]
2015-04-29 18:17               ` Johannes Sixt
2015-04-29 14:42 ` Roberto Tyley

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=xmqqegn26eot.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=cyrus-dev@edla.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.