From: James Pickens <jepicken@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
Johannes Sixt <j.sixt@viscovery.net>,
skillzero@gmail.com, git@vger.kernel.org
Subject: Re: sparse support in pu
Date: Mon, 17 Aug 2009 09:49:17 -0700 [thread overview]
Message-ID: <885649360908170949j3b5dddffq2bb36620187c2bbb@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0908171425410.4991@intel-tinevez-2-302>
On Mon, Aug 17, 2009, Johannes Schindelin<Johannes.Schindelin@gmx.de> wrote:
> The term 'phantom' is not specified at all. At least interested people on
> the mailing list know 'sparse'. But I agree that the naming is a major
> problem, hence my earlier (unanswered) call.
I don't particularly like 'phantom' either, but I haven't come up with any
good alternatives. 'sparse' seems fine to me, though it might make sense
to lengthen it to 'sparse-checkout'.
> However, I would find specifying what you do _not_ want in that file
> rather unintuitive, in the same leage as receive.denyNonFastForwards = no.
>
> If I want to have a sparse checkout, I know which files I _want_.
I agree; specifying which files you don't want seems backwards to me.
James
prev parent reply other threads:[~2009-08-17 16:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 6:09 sparse support in pu skillzero
2009-08-17 8:17 ` Nguyen Thai Ngoc Duy
2009-08-17 8:49 ` skillzero
2009-08-17 9:15 ` Johannes Schindelin
2009-08-17 9:41 ` skillzero
2009-08-17 9:51 ` Johannes Sixt
2009-08-17 9:57 ` Johannes Schindelin
2009-08-17 11:43 ` Nguyen Thai Ngoc Duy
2009-08-17 10:21 ` Nguyen Thai Ngoc Duy
2009-08-17 10:36 ` Johannes Sixt
2009-08-17 11:41 ` Nguyen Thai Ngoc Duy
2009-08-17 12:00 ` Johannes Sixt
2009-08-17 12:19 ` Nguyen Thai Ngoc Duy
2009-08-17 12:29 ` Johannes Schindelin
2009-08-17 12:52 ` Peter Harris
2009-08-17 13:23 ` Johannes Schindelin
2009-08-17 14:30 ` Peter Harris
2009-08-17 16:05 ` Junio C Hamano
2009-08-17 17:13 ` Johannes Schindelin
2009-08-17 12:53 ` Nguyen Thai Ngoc Duy
2009-08-17 16:49 ` James Pickens [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=885649360908170949j3b5dddffq2bb36620187c2bbb@mail.gmail.com \
--to=jepicken@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=pclouds@gmail.com \
--cc=skillzero@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