Re: bug report
- From
- Theodore Li <teddy.litheodore@gmail.com>
- Date
- Nov 12, 2021, 06:59 UTC
- Message-ID
- <CAHPjYFyH+GuBG8QNzD36JhoJWyNnEXfqpn4PUJV0ANF2ertYZg@mail.gmail.com>
- In-Reply-To
- <xmqq8rxuj8s8.fsf@gitster.g>
Yes, though other patterns like !/*/ don't need the quotes. I thought it worked the same way without the quotes in earlier versions, but after testing with version 2.32.0, it seems like the behavior is the same. Guess I remembered wrong.
On Thu, Nov 11, 2021 at 11:30 PM Junio C Hamano <gitster@pobox.com> wrote:
Show 30 quoted lines
> > Theodore Li <teddy.litheodore@gmail.com> writes: > > > Thank you for filling out a Git bug report! > > Please answer the following questions to help us understand your issue. > > > > What did you do before the bug happened? (Steps to reproduce your issue) > > After cloning a remote repository with the --no-checkout option and > > executing git sparse-checkout init, the bug occurs with any > > sparse-checkout command with the /* pattern (i.e. git sparse-checkout > > set /*). > > > > What did you expect to happen? (Expected behavior) > > The contents of .git/info/sparse-checkout and the output of git > > sparse-checkout list should be '/*' > > > > What happened instead? (Actual behavior) > > Instead, the output is the contents of the user's local root directory > > (i.e. /bin, /boot, /cdrom, etc.). > > A blind guess, as I do not use sparse patterns, but perhaps you did > not quote the "/*' pattern, i.e. you typed > > $ git sparse-checkout set /* > > where you would have got a better behaviour if you typed > > $ git sparse-checkout set "/*" > > ?