From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: Duy Nguyen <pclouds@gmail.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCHv8 0/5] pathspec magic extension to search for attributes
Date: Fri, 20 May 2016 10:00:47 -0700 [thread overview]
Message-ID: <xmqq1t4wfyv4.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAGZ79kYx_pX81bmpyXCvJSVsZW=t3VpBizUPQ90Wz9=HdG42UA@mail.gmail.com> (Stefan Beller's message of "Thu, 19 May 2016 14:25:52 -0700")
Stefan Beller <sbeller@google.com> writes:
> Right. But upon finding the new name for clone, I wondered why
> this has to be submodule specific. The attr pathspecs are also working
> with any other files. So if you don't use submodules, I think it would be
> pretty cool to have a
>
> git clone --sparse-checkout=Documentation/ ...
It would be cool, but arent' "sparse" and the various existing
status "submodule" has very different things?
- A submodule can be uninitialized, in which case you do get an empty
directory but you do not see .git in it.
- A path can be excluded by the sparse checkout mechanism, in which
case you do not get _anything_ in the filesystem.
So "git clone --sparse-exclude=Documentation/" that does not waste
diskspace for Documentation/ directory may be an interesting thing
to have, and "git clone --sparse-exclude=submodule-dir/" that does
not even create submodule-dir/ directory may also be, but the latter
is quite different from a submodule that is not initialied in a
superproject that does not use any "sparse" mechanism.
Besides, I think (improved) submodule mechanism would be a good way
forward for scalability, and "sparse" hack is not (primarily because
it still populates the index fully with 5 million entries even when
your attention is narrowed only to a handful of directories with
2000 leaf entries; this misdesign requires other ugly hacks to be
piled on, like untracked cache and split index).
I do not think we want "submodule" to be tied to and dependent on
the latter.
next prev parent reply other threads:[~2016-05-20 17:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 1:09 [PATCHv8 0/5] pathspec magic extension to search for attributes Stefan Beller
2016-05-19 1:09 ` [PATCHv8 1/5] string list: improve comment Stefan Beller
2016-05-19 18:08 ` Junio C Hamano
2016-05-19 18:12 ` Stefan Beller
2016-05-19 1:09 ` [PATCHv8 2/5] Documentation: fix a typo Stefan Beller
2016-05-19 1:09 ` [PATCHv8 3/5] pathspec: move long magic parsing out of prefix_pathspec Stefan Beller
2016-05-19 1:09 ` [PATCHv8 4/5] pathspec: move prefix check out of the inner loop Stefan Beller
2016-05-19 1:09 ` [PATCHv8 5/5] pathspec: allow querying for attributes Stefan Beller
2016-05-19 18:53 ` Junio C Hamano
2016-05-19 20:42 ` Stefan Beller
2016-05-19 21:00 ` Junio C Hamano
2016-05-19 19:37 ` Junio C Hamano
2016-05-19 18:55 ` [PATCHv8 0/5] pathspec magic extension to search " Junio C Hamano
2016-05-19 21:00 ` Stefan Beller
2016-05-19 21:05 ` Junio C Hamano
2016-05-19 21:25 ` Stefan Beller
2016-05-20 17:00 ` Junio C Hamano [this message]
2016-05-20 18:12 ` Stefan Beller
2016-05-20 18:19 ` Junio C Hamano
2016-05-22 11:45 ` Duy Nguyen
2016-05-23 18:49 ` Stefan Beller
2016-05-24 2:00 ` 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
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=xmqq1t4wfyv4.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=sbeller@google.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).