From: Johannes Sixt <j.sixt@viscovery.net>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: skillzero@gmail.com, git@vger.kernel.org
Subject: Re: sparse support in pu
Date: Mon, 17 Aug 2009 14:00:54 +0200 [thread overview]
Message-ID: <4A894676.1090803@viscovery.net> (raw)
In-Reply-To: <fcaeb9bf0908170441o30005085nb0d4e08f333b6146@mail.gmail.com>
Nguyen Thai Ngoc Duy schrieb:
> On Mon, Aug 17, 2009 at 5:36 PM, Johannes Sixt<j.sixt@viscovery.net> wrote:
>> In order to advocate my earlier proposal: Name the file
>> .git/info/phantoms, then it's clear: "The files mentioned here are
>> phantoms" - they exist in the index, but not in the worktree; no phantoms
>> means that everything is checked out.
>
> OK. Phantom checkout, must be unique in VCS world ;-) If no one
> objects my next series will use this name as it's better than "sparse"
> and "assume-unchanged" is just too vague. Would option names to
> enable/disable this be --with[out]-phantoms?
--phantoms vs. --no-phantoms?
-- Hannes
next prev parent reply other threads:[~2009-08-17 12:01 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 [this message]
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
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=4A894676.1090803@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--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