From: skillzero@gmail.com
To: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC PATCH 0/5] Sparse checkout resurrection
Date: Fri, 31 Jul 2009 14:18:26 -0700 [thread overview]
Message-ID: <2729632a0907311418m6e60b1b6g9475f7668dec0192@mail.gmail.com> (raw)
In-Reply-To: <1248850154-5469-1-git-send-email-pclouds@gmail.com>
2009/7/28 Nguyễn Thái Ngọc Duy <pclouds@gmail.com>:
> Hi,
>
> I rip most of the code from my sparse checkout series,
> leaving only basic stuff. Now there is no CE_NO_CHECKOUT bit (CE_VALID
> will be used), no sparse pattterns. You will need to provide a script,
> namely "git-shape-workdir", to specify how you want to shape your
> workdir. That's all. No porcelain, only plumbing. Need to add some
> options to read-tree and checkout in order to enable/disable this, but
> I haven't got that far.
>
> The first four patches is more or less CE_VALID fixups. Real stuff is
> in the last patch. Sparse patterns may return as a separate
> script. Currently no idea how the porcelain UI should be. The only
> thing that is probably impossible this way is "git clone
> --sparse". You may need to "clone -n" first, then apply sparse
> checkout later.
>
> Comments?
I don't know the git code enough to really comment on the details yet,
but I just wanted to say that I'd love to see sparse checkout support
in git. I tried your other patch series using a config variable
instead of the "git-shape-workdir" script and I liked it (although I
didn't thoroughly test it). It shouldn't be hard to write a
git-shape-workdir script to parse a modules file to decide which files
to include/exclude (I'm hoping to do that soon).
Judging by the surprisingly large number of people commenting in the
recent git survey that they want some form of sparse/partial checkout
support (myself included), I hope something like this patch series
gets some traction.
BTW...Is there a repository I can clone from that has these changes
and possibly future enhancements? I checked
<http://repo.or.cz/w/git/pclouds.git>, but I didn't see them.
next prev parent reply other threads:[~2009-07-31 21:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 6:49 [RFC PATCH 0/5] Sparse checkout resurrection Nguyễn Thái Ngọc Duy
2009-07-29 6:49 ` [PATCH 1/5] Prevent diff machinery from examining worktree outside sparse checkout Nguyễn Thái Ngọc Duy
2009-07-29 6:49 ` [PATCH 2/5] grep: skip files outside sparse checkout area Nguyễn Thái Ngọc Duy
2009-07-29 6:49 ` [PATCH 3/5] gitignore: read from index if .gitignore is not in worktree Nguyễn Thái Ngọc Duy
2009-07-29 6:49 ` [PATCH 4/5] unpack_trees(): keep track of unmerged entries Nguyễn Thái Ngọc Duy
2009-07-29 6:49 ` [PATCH 5/5] unpack_trees(): add support for sparse checkout Nguyễn Thái Ngọc Duy
2009-07-29 11:48 ` Jakub Narebski
2009-07-29 23:32 ` Nguyen Thai Ngoc Duy
2009-07-30 0:42 ` Jakub Narebski
2009-07-31 16:55 ` [PATCH 3/5] gitignore: read from index if .gitignore is not in worktree Junio C Hamano
2009-07-31 16:42 ` [PATCH 2/5] grep: skip files outside sparse checkout area Junio C Hamano
2009-08-04 13:14 ` Nguyen Thai Ngoc Duy
2009-07-31 16:34 ` [PATCH 1/5] Prevent diff machinery from examining worktree outside sparse checkout Junio C Hamano
2009-07-31 21:18 ` skillzero [this message]
2009-08-04 13:20 ` [RFC PATCH 0/5] Sparse checkout resurrection Nguyen Thai Ngoc Duy
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=2729632a0907311418m6e60b1b6g9475f7668dec0192@mail.gmail.com \
--to=skillzero@gmail.com \
--cc=git@vger.kernel.org \
--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).