From: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
To: "James Pickens" <jepicken@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC PATCH 00/12] Sparse checkout
Date: Fri, 25 Jul 2008 06:23:47 +0700 [thread overview]
Message-ID: <fcaeb9bf0807241623m3fbd476dyc41990d8ef0888e6@mail.gmail.com> (raw)
In-Reply-To: <loom.20080724T171151-310@post.gmane.org>
On 7/25/08, James Pickens <jepicken@gmail.com> wrote:
> > You can do that with "git checkout --path" (non-recursive checkout aside):
> >
> > $ git checkout --path=A # checkout full A
> > $ git checkout --path=A/B1/C1 # no, limit to A/B1/C1 only
> > $ git checkout --path=A/B1/C1:A/B2 # extend to A/B2 too
>
>
> My point was not that incremental checkout is impossible, just that it
> would be easier if I didn't have to re-type the full path list again.
> Suppose I had 9 directories (A/B1 through A/B9) in my sparse checkout,
> and I wanted to add a 10th directory (A/B10). It would be much easier
> to type something like
>
> $ cd A
> $ git checkout B10
>
> instead of
>
> $ git checkout --path=A/B1:A/B2:A/B3:A/B4:A/B5:A/B6:A/B7:A/B8:A/B9:A/B10
"git checkout B10" form has already been taken. How about "git
checkout --add-path" and "git checkout --remove-path"?
--
Duy
next prev parent reply other threads:[~2008-07-24 23:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 14:55 [RFC PATCH 00/12] Sparse checkout Nguyễn Thái Ngọc Duy
2008-07-23 15:38 ` Nguyen Thai Ngoc Duy
2008-07-23 16:15 ` Johannes Schindelin
2008-07-23 16:21 ` Nguyen Thai Ngoc Duy
2008-07-23 16:55 ` Johannes Schindelin
2008-07-24 8:27 ` Nguyen Thai Ngoc Duy
2008-07-24 12:42 ` Johannes Schindelin
2008-07-24 13:29 ` Nguyen Thai Ngoc Duy
2008-07-24 13:44 ` Johannes Schindelin
2008-07-24 13:50 ` Nguyen Thai Ngoc Duy
2008-07-24 16:22 ` Avery Pennarun
2008-07-24 16:38 ` Johannes Schindelin
2008-07-24 18:59 ` Nguyen Thai Ngoc Duy
2008-08-03 18:37 ` Jan Hudec
2008-08-03 20:48 ` Johannes Schindelin
2008-08-04 12:29 ` Nguyen Thai Ngoc Duy
2008-07-24 8:24 ` James Pickens
2008-07-24 9:00 ` Nguyen Thai Ngoc Duy
2008-07-24 17:59 ` James Pickens
2008-07-24 23:23 ` Nguyen Thai Ngoc Duy [this message]
2008-07-24 23:38 ` James Pickens
2008-07-24 9:35 ` Jakub Narebski
2008-07-24 10:58 ` Nguyen Thai Ngoc Duy
2008-07-24 20:01 ` Jakub Narebski
2008-07-24 23:21 ` Nguyen Thai Ngoc Duy
2008-07-25 14:53 ` Avery Pennarun
2008-07-25 0:07 ` Johannes Schindelin
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=fcaeb9bf0807241623m3fbd476dyc41990d8ef0888e6@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=jepicken@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).