git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Elijah Newren <newren@gmail.com>
To: William Sprent via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Victoria Dye <vdye@github.com>,
	William Sprent <williams@unity3d.com>
Subject: Re: [PATCH v2 0/2] builtin/sparse-checkout: add check-rules command
Date: Sat, 1 Apr 2023 11:49:42 -0700	[thread overview]
Message-ID: <CABPp-BHhjjO32EAzi_Deck6fxsyG=uMrvAnJLaD0e9qMtrcDEQ@mail.gmail.com> (raw)
In-Reply-To: <pull.1488.v2.git.1679903703.gitgitgadget@gmail.com>

Hi,

On Mon, Mar 27, 2023 at 12:55 AM William Sprent via GitGitGadget
<gitgitgadget@gmail.com> wrote:
>
> Hi
>
> This v2 addresses comments from Elijah's review comments.
>
> There's one thing worth highlighting. Elijah pointed out that the the
> "check-rules cone mode is default" test would be stronger if the test itself
> started with a 'git sparse-checkout set --no-cone' to explicitly test that
> the default interpretation of the rules passed with the '--rules-file'
> option is cone mode even though the current checkout is non-cone. I
> implemented this and it exposed that the option did not actually behave that
> way, and that the test only verified the default behaviour of a bare
> repository.
>
> I've modified the logic of the '--rules-file' option such that it defaults
> to cone mode unless combined with '--no-cone', and I've added a line to the
> documentation to make this more explicit.
>
> The alternative would be to have '--rules-file' assume non cone mode when in
> a non cone mode checkout, but I think this depends a bit on "how deprecated"
> non-cone mode is vs. how important it is to have the option behave
> consistently with 'sparse-checkout set' (which respects the current
> checkout).

Ooh, nice catch.

Given that the whole point of check-rules and --rules-file is to
determine how a _different_ sparse checkout would behave, I agree with
your decision here that the current sparse checkout should not affect
how --rules-file functions.

>
> Changes since v1:
>
>  * Explicitly state in documentation that '--rules-file' expects newline
>    separated rules.
>  * Explicitly state in documentation that '-z' does not affect the
>    '--rules-file' input.
>  * Fixup typo where 'When called with the --rules-file <file> flag' was
>    missing "flag".
>  * Fixup behaviour in 'check-rules --rules-file', such that it defaults to
>    accepting cone mode patterns when in a non cone checkout.
>  * Remember to release string buffers in 'check_rules()'.
>  * Explicitly state in documentation that '--rules-file' defaults to cone
>    mode unless combined with '--no-cone'.
>  * Better test that the default of '--rules-file' is to expect '--cone-mode'
>    by running 'check-rules' in a non-cone mode checkout.

This round addresses all my issues, and I agree with the other change
made in this round.  So, v2 is:

Reviewed-by: Elijah Newren <newren@gmail.com>

Thanks for sending this in, William!

  parent reply	other threads:[~2023-04-01 18:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08 13:49 [PATCH 0/2] builtin/sparse-checkout: add check-rules command William Sprent via GitGitGadget
2023-03-08 13:49 ` [PATCH 1/2] builtin/sparse-checkout: remove NEED_WORK_TREE flag William Sprent via GitGitGadget
2023-03-08 18:14   ` Junio C Hamano
2023-03-08 19:27     ` Junio C Hamano
2023-03-09 15:31       ` Elijah Newren
2023-03-09 22:19         ` Junio C Hamano
2023-03-08 13:49 ` [PATCH 2/2] builtin/sparse-checkout: add check-rules command William Sprent via GitGitGadget
2023-03-19  4:26   ` Elijah Newren
2023-03-20 15:49     ` William Sprent
2023-03-19  4:28 ` [PATCH 0/2] " Elijah Newren
2023-03-27  7:55 ` [PATCH v2 " William Sprent via GitGitGadget
2023-03-27  7:55   ` [PATCH v2 1/2] builtin/sparse-checkout: remove NEED_WORK_TREE flag William Sprent via GitGitGadget
2023-03-27 17:51     ` Junio C Hamano
2023-04-07 16:16       ` SZEDER Gábor
2023-04-07 16:38         ` Junio C Hamano
2023-03-27  7:55   ` [PATCH v2 2/2] builtin/sparse-checkout: add check-rules command William Sprent via GitGitGadget
2023-04-01 18:49   ` Elijah Newren [this message]
2023-04-03 17:07     ` [PATCH v2 0/2] " Junio C Hamano

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='CABPp-BHhjjO32EAzi_Deck6fxsyG=uMrvAnJLaD0e9qMtrcDEQ@mail.gmail.com' \
    --to=newren@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=vdye@github.com \
    --cc=williams@unity3d.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).