From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Nikolay Borisov <nik.borisov@suse.com>, git@vger.kernel.org
Subject: Re: [PATCH] rebase: Fix documentation about used shell in -x
Date: Tue, 16 Jan 2024 09:58:01 -0800 [thread overview]
Message-ID: <xmqq5xzt17py.fsf@gitster.g> (raw)
In-Reply-To: <20240116143757.GA2119690@coredump.intra.peff.net> (Jeff King's message of "Tue, 16 Jan 2024 09:37:57 -0500")
Jeff King <peff@peff.net> writes:
> Maybe it makes sense to just say:
>
> ...in a shell (the default one, usually /bin/sh), ...
>
> It might even make sense to just drop the parenthetical phrase entirely.
> Git executes lots of things using a shell, and it is always "the default
> one", but we don't bother saying so in most places.
Thanks for your archaeological skill, as always. I like the
deliberate "vagueness" of the above.
next prev parent reply other threads:[~2024-01-16 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 14:18 [PATCH] rebase: Fix documentation about used shell in -x Nikolay Borisov
2024-01-16 14:37 ` Jeff King
2024-01-16 17:58 ` Junio C Hamano [this message]
2024-01-16 16:50 ` Kristoffer Haugsbakk
2024-01-17 22:35 ` Junio C Hamano
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=xmqq5xzt17py.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=nik.borisov@suse.com \
--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;
as well as URLs for NNTP newsgroup(s).