From: Junio C Hamano <gitster@pobox.com>
To: Derrick Stolee <stolee@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2021, #04; Mon, 13)
Date: Tue, 14 Sep 2021 10:47:55 -0700 [thread overview]
Message-ID: <xmqq7dfj2gms.fsf@gitster.g> (raw)
In-Reply-To: <88bb51c3-b5ab-77df-f9fb-b9252c2b0fa6@gmail.com> (Derrick Stolee's message of "Tue, 14 Sep 2021 09:33:29 -0400")
Derrick Stolee <stolee@gmail.com> writes:
> Perhaps this would be a good summary?
>
> "git add", "git mv", and "git rm" have been adjusted to avoid
> updating paths outside of the sparse-checkout definition unless
> the user specifies a "--sparse" option.
Let me steal that. A correction to the topic summary like this is
very much appreciated.
next prev parent reply other threads:[~2021-09-14 17:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 2:02 What's cooking in git.git (Sep 2021, #04; Mon, 13) Junio C Hamano
2021-09-14 4:13 ` Elijah Newren
2021-09-14 5:43 ` Taylor Blau
2021-09-14 13:33 ` Derrick Stolee
2021-09-14 17:47 ` Junio C Hamano [this message]
2021-09-14 19:47 ` Jeff Hostetler
2021-09-14 20:51 ` Junio C Hamano
2021-09-14 20:57 ` Jeff Hostetler
2021-09-14 19:54 ` Philip Oakley
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=xmqq7dfj2gms.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=stolee@gmail.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).