From: Victoria Dye <vdye@github.com>
To: fawaz ahmed0 <fawazahmed0@hotmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: "reject arguments in cone-mode that look like patterns" doesn't work in macos-12
Date: Thu, 14 Jul 2022 12:18:51 -0700 [thread overview]
Message-ID: <4f4d5d03-2a0d-19c1-fd2e-80ab86aa1145@github.com> (raw)
In-Reply-To: <BL0PR13MB427533B25CCFE6A37F7619E8F1889@BL0PR13MB4275.namprd13.prod.outlook.com>
fawaz ahmed0 wrote:
> Please refer: https://github.com/git/git/commit/8dd7c4739bded62175bea1f7518d993b39b51f90#commitcomment-78433458
>
>
> Using patterns in cone mode should fail, but it doesn't seem to fail on macOS-12(github actions)
Can you confirm which version is being used on that MacOS agent? For
example, you could add a call to 'git version' in the workflow and see what
it prints out. I suspect that the agent may be using an older version of
Git, which would mean that the sparse-checkout is initialized in *non* cone
mode.
For what it's worth, my local development machine is also MacOS 12 (running
Git v2.37), and I'm correctly seeing the error in a cone mode
sparse-checkout.
>
> Step to reproduce(try in macOS-12):
>
> git clone --filter=blob:none --no-checkout --depth 1 --sparse https://github.com/fawazahmed0/currency-api.git .
> git sparse-checkout add 'latest/*'
>
> Thanks
> Fawaz Ahmed
next prev parent reply other threads:[~2022-07-14 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BL0PR13MB42750BC5C4837B7B0BD1885EF1889@BL0PR13MB4275.namprd13.prod.outlook.com>
2022-07-14 8:00 ` "reject arguments in cone-mode that look like patterns" doesn't work in macos-12 fawaz ahmed0
2022-07-14 19:18 ` Victoria Dye [this message]
[not found] ` <BL0PR13MB427538CEAD5481CCBF6D195DF1889@BL0PR13MB4275.namprd13.prod.outlook.com>
2022-07-14 19:47 ` Victoria Dye
2022-07-14 20:05 ` fawaz ahmed0
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=4f4d5d03-2a0d-19c1-fd2e-80ab86aa1145@github.com \
--to=vdye@github.com \
--cc=fawazahmed0@hotmail.com \
--cc=git@vger.kernel.org \
/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).