git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Elijah Newren <newren@gmail.com>
To: Alasdair Hurst <alasdairhurst@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git sparse-checkout set not working in git 2.27.0
Date: Thu, 11 Jun 2020 11:30:07 -0700	[thread overview]
Message-ID: <CABPp-BFRX3MPn=jw+Ezdx1pmxVF9SJw7Mxhk5cS5KUrXFJmM=w@mail.gmail.com> (raw)
In-Reply-To: <000801d64010$565b0b70$03112250$@gmail.com>

On Thu, Jun 11, 2020 at 9:52 AM Alasdair Hurst <alasdairhurst@gmail.com> wrote:
>
> In git 2.27.0 sparse-checkout doesn't seem to work the same as it did in
> 2.25.0:
>
>
>
> Version: git version 2.27.0.windows.1 (the same behavior occurs on 2.27.0 on
> linux too)
>
> Commands:
> -git clone git@repo.com:user/repo <mailto:git@repo.com:user/repo>
> --no-checkout --depth 1 sparse-repo
>
> -cd sparse-repo
>
> -git sparse-checkout init
>
> -git sparse-checkout add packages
>
>
>
> Expected behavior (as seen in 0.25):
>
> -ls
> packages
>
> The packages directory is checked out and available the repo root.
>
>
> Current behavior
>
> -ls
>
>
>
> No packages directory is checked out and the root is empty.

Thanks for the report; this was fixed by commit b5bfc08a97
("sparse-checkout: avoid staging deletions of all files", 2020-06-05),
currently cooking in the 'next' branch of git.git.  See the thread at
https://lore.kernel.org/git/pull.801.v2.git.git.1591324899170.gitgitgadget@gmail.com/
if you want to read up on it.

      reply	other threads:[~2020-06-11 18:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 16:49 git sparse-checkout set not working in git 2.27.0 Alasdair Hurst
2020-06-11 18:30 ` Elijah Newren [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='CABPp-BFRX3MPn=jw+Ezdx1pmxVF9SJw7Mxhk5cS5KUrXFJmM=w@mail.gmail.com' \
    --to=newren@gmail.com \
    --cc=alasdairhurst@gmail.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).