git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2021, #05; Fri, 17)
Date: Mon, 20 Sep 2021 10:00:52 -0400	[thread overview]
Message-ID: <922bdab1-c521-84b5-51c1-a0413fd67394@gmail.com> (raw)
In-Reply-To: <xmqqlf3ug3q7.fsf@gitster.g>

On 9/17/2021 7:52 PM, Junio C Hamano wrote:
...
> * ds/add-rm-with-sparse-index (2021-09-12) 14 commits
>  - advice: update message to suggest '--sparse'
>  - mv: refuse to move sparse paths
>  - rm: skip sparse paths with missing SKIP_WORKTREE
>  - rm: add --sparse option
>  - add: update --renormalize to skip sparse paths
>  - add: update --chmod to skip sparse paths
>  - add: implement the --sparse option
>  - add: skip tracked paths outside sparse-checkout cone
>  - add: fail when adding an untracked sparse file
>  - dir: fix pattern matching on dirs
>  - dir: select directories correctly
>  - dir: extract directory-matching logic
>  - t1092: behavior for adding sparse files
>  - t3705: test that 'sparse_entry' is unstaged
>  (this branch uses ds/mergies-with-sparse-index and ds/sparse-index-ignored-files.)
> 
>  "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.
> 
>  Will merge to 'next'?

I plan to send one more version in response to Elijah's comments.
It should be ready later today.

Thanks,
-Stolee

      parent reply	other threads:[~2021-09-20 14:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-17 23:52 What's cooking in git.git (Sep 2021, #05; Fri, 17) Junio C Hamano
2021-09-18  0:51 ` Taylor Blau
2021-09-18 11:16 ` Carlo Arenas
2021-09-20 14:00 ` Derrick Stolee [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=922bdab1-c521-84b5-51c1-a0413fd67394@gmail.com \
    --to=stolee@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).