From: Matheus Tavares Bernardino <matheus.bernardino@usp.br>
To: Junio C Hamano <gitster@pobox.com>
Cc: git <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Apr 2021, #05; Mon, 19)
Date: Tue, 20 Apr 2021 10:23:38 -0300 [thread overview]
Message-ID: <CAHd-oW7n-wc+TBYjZ1sh6tPc18mB2pXyBh5L382rG72+0RGafw@mail.gmail.com> (raw)
In-Reply-To: <xmqqtuo17t6t.fsf@gitster.g>
Hi, Junio
On Mon, Apr 19, 2021 at 8:25 PM Junio C Hamano <gitster@pobox.com> wrote:
>
> * mt/add-rm-in-sparse-checkout (2021-04-08) 7 commits
> - rm: honor sparse checkout patterns
> - add: warn when asked to update SKIP_WORKTREE entries
> - refresh_index(): add flag to ignore SKIP_WORKTREE entries
> - pathspec: allow to ignore SKIP_WORKTREE entries on index matching
> - add: make --chmod and --renormalize honor sparse checkouts
> - t3705: add tests for `git add` in sparse checkouts
> - add: include magic part of pathspec on --refresh error
>
> "git add" and "git rm" learned not to touch those paths that are
> outside of sparse checkout.
Oops, sorry I ended up not replying to your recent message [1] about
whether or not this was ready for 'next'. But yeah, I don't have any
pending changes planned; I think it's ready :) Elijah also signaled he
is OK with the current version [2].
[1]: https://lore.kernel.org/git/xmqqzgxxkj8v.fsf@gitster.g/
[2]: https://lore.kernel.org/git/CABPp-BE=KfQTj0ad3uBS90MA1EDkHFV8kXi7xbEMDcnoi-MiOg@mail.gmail.com/
next prev parent reply other threads:[~2021-04-20 13:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 23:25 What's cooking in git.git (Apr 2021, #05; Mon, 19) Junio C Hamano
2021-04-20 13:23 ` Matheus Tavares Bernardino [this message]
2021-04-20 13:52 ` Ævar Arnfjörð Bjarmason
2021-04-20 22:15 ` Junio C Hamano
2021-04-20 23:14 ` brian m. carlson
2021-04-21 8:26 ` Ævar Arnfjörð Bjarmason
2021-04-21 22:32 ` brian m. carlson
2021-04-20 23:51 ` Junio C Hamano
2021-04-23 14:41 ` Jeff King
2021-04-20 14:28 ` Jeff Hostetler
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=CAHd-oW7n-wc+TBYjZ1sh6tPc18mB2pXyBh5L382rG72+0RGafw@mail.gmail.com \
--to=matheus.bernardino@usp.br \
--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).