From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Wink Saville <wink@saville.com>, Git List <git@vger.kernel.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [RFC PATCH v4] rebase: Update invocation of rebase dot-sourced scripts
Date: Fri, 23 Mar 2018 14:01:33 -0700 [thread overview]
Message-ID: <xmqqbmfeik0i.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CAPig+cQG16AhLPMeOFAw1GF81oXivFSDHvQ5B8kX20YGAT_BxQ@mail.gmail.com> (Eric Sunshine's message of "Fri, 23 Mar 2018 02:26:55 -0400")
Eric Sunshine <sunshine@sunshineco.com> writes:
>> When it was discovered that some shell implementations
> ...
> ECANTPARSE: This paragraph is grammatically corrupt.
>
> ECANTPARSE: Grammatically corrupt.
> ...
> (despite the run-on sentence in the first paragraph and the apparent
> incorrect explanation of top-level "return" misbehavior -- the in-code
> comment says top-level "return" was essentially a no-op in broken
> shells, whereas he said it exited the shell).
My bad, almost entirely. Sorry.
next prev parent reply other threads:[~2018-03-23 21:01 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 4:39 [RFC PATCH v4] rebase-interactive Wink Saville
2018-03-23 4:39 ` [RFC PATCH v4] rebase-interactive: Simplify pick_on_preserving_merges Wink Saville
2018-03-23 17:10 ` Johannes Schindelin
2018-03-23 4:39 ` [RFC PATCH v4] rebase: Update invocation of rebase dot-sourced scripts Wink Saville
2018-03-23 6:26 ` Eric Sunshine
2018-03-23 21:01 ` Junio C Hamano [this message]
2018-03-23 21:18 ` Eric Sunshine
2018-03-23 17:12 ` Johannes Schindelin
2018-03-23 19:06 ` Wink Saville
2018-03-23 20:51 ` Junio C Hamano
2018-03-23 21:05 ` Wink Saville
2018-03-23 21:25 ` [RFC PATCH v5 0/8] rebase-interactive Wink Saville
2018-03-23 21:34 ` Wink Saville
2018-03-23 22:39 ` Junio C Hamano
2018-03-23 22:54 ` Wink Saville
2018-03-24 5:36 ` Wink Saville
2018-03-26 15:56 ` Junio C Hamano
2018-03-26 17:01 ` Jeff Hostetler
2018-03-26 17:57 ` Junio C Hamano
2018-03-26 18:22 ` Jeff Hostetler
2018-03-27 5:07 ` Junio C Hamano
2018-03-27 10:03 ` Jeff Hostetler
2018-03-26 18:00 ` Junio C Hamano
2018-03-26 18:33 ` Jeff Hostetler
2018-03-26 18:43 ` Wink Saville
2018-03-26 19:37 ` Junio C Hamano
2018-03-26 22:35 ` Johannes Schindelin
2018-03-23 22:27 ` Junio C Hamano
2018-03-23 21:25 ` [RFC PATCH v5 1/8] rebase-interactive: simplify pick_on_preserving_merges Wink Saville
2018-03-23 21:25 ` [RFC PATCH v5 2/8] rebase: update invocation of rebase dot-sourced scripts Wink Saville
2018-03-23 21:25 ` [RFC PATCH v5 3/8] Indent function git_rebase__interactive Wink Saville
2018-03-23 22:12 ` Junio C Hamano
2018-03-23 22:52 ` Wink Saville
2018-03-23 23:06 ` Junio C Hamano
2018-03-24 0:01 ` Wink Saville
2018-03-23 21:25 ` [RFC PATCH v5 4/8] Extract functions out of git_rebase__interactive Wink Saville
2018-03-23 22:22 ` Junio C Hamano
2018-03-24 7:20 ` Eric Sunshine
2018-03-23 21:25 ` [RFC PATCH v5 5/8] Add and use git_rebase__interactive__preserve_merges Wink Saville
2018-03-23 21:25 ` [RFC PATCH v5 6/8] Remove unused code paths from git_rebase__interactive Wink Saville
2018-03-23 21:25 ` [RFC PATCH v5 7/8] Remove unused code paths from git_rebase__interactive__preserve_merges Wink Saville
2018-03-23 21:25 ` [RFC PATCH v5 8/8] Remove merges_option and a blank line Wink Saville
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=xmqqbmfeik0i.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.com \
--cc=wink@saville.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).