From: "Kirill Müller" <kirill.mueller@ivt.baug.ethz.ch>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] checkout: add --sparse for restoring files in sparse checkout mode
Date: Sun, 24 Mar 2013 20:50:08 +0100 [thread overview]
Message-ID: <514F58F0.1050909@ivt.baug.ethz.ch> (raw)
In-Reply-To: <20130324181752.GA4543@elie.Belkin>
Hi
On 03/24/2013 07:17 PM, Jonathan Nieder wrote:
> Hi,
>
> Nguyễn Thái Ngọc Duy wrote:
>
>> --- a/Documentation/git-checkout.txt
>> +++ b/Documentation/git-checkout.txt
>> @@ -180,6 +180,13 @@ branch by running "git rm -rf ." from the top level of the working tree.
>> Afterwards you will be ready to prepare your new files, repopulating the
>> working tree, by copying them from elsewhere, extracting a tarball, etc.
>>
>> +
>> +--sparse::
>> + In sparse checkout mode, `git checkout -- <paths>` would
>> + update all entries matched by <paths> regardless sparse
>> + patterns. This option only updates entries matched by <paths>
>> + and sparse patterns.
> Hm, should this be the default?
>
> In principle, I would expect
>
> git checkout -- .
>
> to make the worktree match the index, respecting the sparse checkout.
> And something like
>
> git checkout --widen -- .
>
> to change the sparse checkout pattern. But of course it is easily
> possible that I am missing some details of how sparse checkout is
> used in practice.
>
> What do you think?
Thank you for your opinion. I'd second that. When I do a sparse
checkout, I want to see only the directories I have included and not
excluded, unless I explicitly change that.
-Kirill
next prev parent reply other threads:[~2013-03-24 19:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 10:28 Hard reset of a subdirectory in a sparse checkout setting Kirill Müller
2013-03-23 9:59 ` Duy Nguyen
2013-03-23 13:02 ` Kirill Müller
2013-03-24 5:06 ` [PATCH] checkout: add --sparse for restoring files in sparse checkout mode Nguyễn Thái Ngọc Duy
2013-03-24 6:12 ` Eric Sunshine
2013-03-24 18:17 ` Jonathan Nieder
2013-03-24 19:50 ` Kirill Müller [this message]
2013-03-25 1:34 ` Duy Nguyen
2013-03-25 1:57 ` Jonathan Nieder
2013-03-30 10:02 ` [PATCH v2] checkout: add --no-widen " Nguyễn Thái Ngọc Duy
2013-04-01 4:48 ` Jonathan Nieder
2013-04-01 5:12 ` Junio C Hamano
2013-04-01 5:13 ` Duy Nguyen
2013-04-01 6:18 ` Jonathan Nieder
2013-04-12 23:12 ` [PATCH v3] checkout: add --ignore-skip-worktree-bits " Nguyễn Thái Ngọc Duy
2013-05-14 9:27 ` Müller Kirill
2013-05-14 10:21 ` Duy Nguyen
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=514F58F0.1050909@ivt.baug.ethz.ch \
--to=kirill.mueller@ivt.baug.ethz.ch \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=pclouds@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;
as well as URLs for NNTP newsgroup(s).