Git development
 help / color / mirror / Atom feed
From: Mirko Faina <mroik@delayed.space>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>,
	 Elijah Newren <newren@gmail.com>,
	Derrick Stolee <stolee@gmail.com>,
	 Mirko Faina <mroik@delayed.space>
Subject: Re: [RFC PATCH 0/6] Introduce precious files
Date: Thu, 8 Oct 2026 14:12:47 +0200	[thread overview]
Message-ID: <aseIX3hABbm822X8@exploit> (raw)
In-Reply-To: <cover.1791460418.git.mroik@delayed.space>

On Thu, Oct 08, 2026 at 02:06:56PM +0200, Mirko Faina wrote:
> Introduce precious files based on Elijah Newren's document [1].
> 
> With this series documentation is not updated yet but I wanted some feedback
> before polishing and moving on to implement the changes for "git clean".
> 
> [1] https://lore.kernel.org/git/pull.1627.git.1703643931314.gitgitgadget@gmail.com/
> 
> [1/6] precious-files.txt: new document proposing new precious file type (Elijah Newren)
> [2/6] dir.h: replace pattern macros with enum in attr.h (Mirko Faina)
> [3/6] dir.c: teach parse_path_pattern() precious files (Mirko Faina)
> [4/6] dir.c: teach add_pattern() reject precious pattern (Mirko Faina)
> [5/6] unpack-trees: teach check_ok_to_remove() precious (Mirko Faina)
> [6/6] builtin/ls-files.c: support for precious files (Mirko Faina)
> 
>  Documentation/technical/precious-files.txt | 540 +++++++++++++++++++++
>  attr.c                                     |   8 +-
>  attr.h                                     |  10 +-
>  builtin/check-ignore.c                     |   1 +
>  builtin/clean.c                            |   4 +-
>  builtin/ls-files.c                         |  75 ++-
>  builtin/sparse-checkout.c                  |  16 +-
>  dir.c                                      | 144 +++++-
>  dir.h                                      |  51 +-
>  t/helper/test-path-walk.c                  |   2 +-
>  t/t1091-sparse-checkout-builtin.sh         |   8 +
>  t/t2205-add-worktree-config.sh             |   2 +-
>  t/t3001-ls-files-others-exclude.sh         |  27 ++
>  t/t7508-status.sh                          |   9 +
>  unpack-trees.c                             |   7 +-
>  15 files changed, 849 insertions(+), 55 deletions(-)
>  create mode 100644 Documentation/technical/precious-files.txt
> 
> -- 
> 2.56.0

I forgot to specify the base. The series is based on c46c1e3772 (Start Git 2.98
cycle, 2026-09-30).

      parent reply	other threads:[~2026-10-08 12:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08 12:06 [RFC PATCH 0/6] Introduce precious files Mirko Faina
2026-10-08 12:06 ` [RFC PATCH 1/6] precious-files.txt: new document proposing new precious file type Mirko Faina
2026-10-08 12:06 ` [RFC PATCH 2/6] dir.h: replace pattern macros with enum in attr.h Mirko Faina
2026-10-08 12:06 ` [RFC PATCH 3/6] dir.c: teach parse_path_pattern() precious files Mirko Faina
2026-10-08 12:07 ` [RFC PATCH 4/6] dir.c: teach add_pattern() reject precious pattern Mirko Faina
2026-10-08 12:07 ` [RFC PATCH 5/6] unpack-trees: teach check_ok_to_remove() precious Mirko Faina
2026-10-08 12:07 ` [RFC PATCH 6/6] builtin/ls-files.c: support for precious files Mirko Faina
2026-10-08 12:12 ` Mirko Faina [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=aseIX3hABbm822X8@exploit \
    --to=mroik@delayed.space \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=newren@gmail.com \
    --cc=peff@peff.net \
    --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