From: Sverre Rabbelier <srabbelier@gmail.com>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: Avery Pennarun <apenwarr@gmail.com>,
Elijah Newren <newren@gmail.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
git <git@vger.kernel.org>
Subject: Re: Sparse clones (Was: Re: [PATCH 1/2] upload-pack: support subtree packing)
Date: Wed, 28 Jul 2010 09:48:01 -0500 [thread overview]
Message-ID: <AANLkTi=e37AGx-Pehe_PPn-0swxrf9Gowekm4cN80G1C@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=zgbT=uw=t18mBUHMxg050pMx_YD835Gbontph@mail.gmail.com>
Heya,
On Wed, Jul 28, 2010 at 02:59, Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:
> Doesn't assume-unchanged bit or sparse checkout help?
See my earlier part, assume-unchanged doesn't help due to the
gitignore files. Sparse checkout isn't an option since I really need
those files to be there, I just don't ever modify them. Really what I
need is read-only checkout ;). "Git, please ignore the existence of
this directory and all it's files/subdirectories, ktnx".
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2010-07-28 14:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 0:13 Sparse clones (Was: Re: [PATCH 1/2] upload-pack: support subtree packing) Elijah Newren
2010-07-28 1:05 ` Avery Pennarun
2010-07-28 3:06 ` Nguyen Thai Ngoc Duy
2010-07-28 3:38 ` Nguyen Thai Ngoc Duy
2010-07-28 3:58 ` Avery Pennarun
2010-07-28 6:12 ` Sverre Rabbelier
2010-07-28 7:59 ` Nguyen Thai Ngoc Duy
2010-07-28 14:48 ` Sverre Rabbelier [this message]
2010-07-28 7:11 ` Nguyen Thai Ngoc Duy
2010-07-28 3:31 ` Elijah Newren
2010-07-31 22:36 ` Elijah Newren
2010-07-28 3:36 ` Nguyen Thai Ngoc Duy
2010-07-28 3:59 ` Elijah Newren
2010-07-29 10:29 ` Nguyen Thai Ngoc Duy
2010-08-13 17:31 ` Enrico Weigelt
2010-08-13 19:19 ` Truncating history (Re: Sparse clones) Jonathan Nieder
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='AANLkTi=e37AGx-Pehe_PPn-0swxrf9Gowekm4cN80G1C@mail.gmail.com' \
--to=srabbelier@gmail.com \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
--cc=pclouds@gmail.com \
--cc=spearce@spearce.org \
/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).