git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Jan 2022, #04; Fri, 14)
Date: Mon, 17 Jan 2022 10:30:51 -0800	[thread overview]
Message-ID: <xmqq35lmw6xw.fsf@gitster.g> (raw)
In-Reply-To: <CABPp-BEROAzba2jDrBhyq1tzZZDYUqROAUGTNp4fNOHfYB3vOg@mail.gmail.com> (Elijah Newren's message of "Sat, 15 Jan 2022 20:25:53 -0800")

Elijah Newren <newren@gmail.com> writes:

> On Sat, Jan 15, 2022 at 9:25 AM Junio C Hamano <gitster@pobox.com> wrote:
>>
>> * en/present-despite-skipped (2022-01-14) 6 commits
>>  - Accelerate clear_skip_worktree_from_present_files() by caching
>>  - Update documentation related to sparsity and the skip-worktree bit
>>  - repo_read_index: clear SKIP_WORKTREE bit from files present in worktree
>>  - unpack-trees: fix accidental loss of user changes
>>  - t1011: add testcase demonstrating accidental loss of user modifications
>>  - Merge branch 'vd/sparse-clean-etc' into en/present-despite-skipped
>>  (this branch uses vd/sparse-clean-etc.)
>>
>>  (NEEDSWORK: BY DOING WHAT), cope better with files on the working
>>  tree that should not exist according to the sparse checkout
>>  settings.
>>  source: <pull.1114.v2.git.1642175983.gitgitgadget@gmail.com>
>
> Perhaps:
>
> In sparse-checkouts, files mis-marked as missing from the working tree
> could lead to later problems.  Such files were hard to discover, and
> harder to correct.  Automatically detecting and correcting the marking
> of such files has been added to avoid these problems.

Thanks.

  reply	other threads:[~2022-01-17 18:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-15  4:37 What's cooking in git.git (Jan 2022, #04; Fri, 14) Junio C Hamano
2022-01-16  4:25 ` Elijah Newren
2022-01-17 18:30   ` Junio C Hamano [this message]
2022-01-18 15:56 ` ab/grep-patterntype (was: What's cooking in git.git (Jan 2022, #04; Fri, 14)) Ævar Arnfjörð Bjarmason
2022-01-18 15:59 ` ab/config-based-hooks-2 " Ævar Arnfjörð Bjarmason
2022-01-18 19:49   ` Glen Choo
2022-01-19 21:32     ` Emily Shaffer
2022-01-18 20:26   ` ab/config-based-hooks-2 Junio C Hamano
2022-01-18 16:08 ` ds/sparse-checkout-requires-per-worktree-config (was Re: What's cooking in git.git (Jan 2022, #04; Fri, 14)) Derrick Stolee
2022-01-18 20:27   ` Junio C Hamano
2022-01-19  0:38 ` ar/submodule-update " Glen Choo
2022-01-19  0:53   ` Junio C Hamano
2022-01-19 20:06 ` What's cooking in git.git (Jan 2022, #04; Fri, 14) Phillip Wood

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq35lmw6xw.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=newren@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).