From: Chris Packham <judge.packham@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: question (possibly) on git subtree/submodules
Date: Fri, 23 Jul 2010 11:35:10 -0700 [thread overview]
Message-ID: <4C49E0DE.8050506@gmail.com> (raw)
In-Reply-To: <20100723171859.GG2507@burratino>
On 23/07/10 10:18, Jonathan Nieder wrote:
> Chris Packham wrote:
>
>> The short answer is no. Nothing git has currently will let you clone a
>> subset of files. Shallow clones exist if you want all the code and the
>> last X changes. The reason for this is git, like other DVCSes, tracks
>> _changes_ rather than _files_ this is something that took me a while to
>> get my head around when I was learning git.
>
> Not quite as cut-and-dried as it may sound, I think. Internally git
> compresses blobs (and other objects) by comparing them to other ones,
> but I do not think that is what you are talking about, and I do not
> see what that has to do with partial clones. In fact, the main reason
> I can see that partial clones (in the sense of getting all metadata
> but not all blobs) are not implemented is that no one has written code
> for it yet.
>
> Here is a thread on related work[1]. Maybe someone else can find a
> more pertinent link.
>
OK I think I must have read to much into the "tracks changes" part,
thanks for pointing it out.
next prev parent reply other threads:[~2010-07-23 18:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 14:00 question (possibly) on git subtree/submodules Maurizio Vitale
2010-07-23 16:56 ` Chris Packham
2010-07-23 17:18 ` Jonathan Nieder
2010-07-23 18:35 ` Chris Packham [this message]
2010-07-27 10:56 ` Alex
2010-07-27 12:48 ` Jakub Narebski
2010-07-27 14:24 ` RFC: Sparse checkout improvements (was: Re: question (possibly) on git subtree/submodules) Marc Branchaud
2010-07-27 16:55 ` skillzero
2010-07-28 13:42 ` RFC: Sparse checkout improvements Marc Branchaud
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=4C49E0DE.8050506@gmail.com \
--to=judge.packham@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.