From: Christian Jaeger <christian@jaeger.mine.nu>
To: Andreas Ericsson <ae@op5.se>
Cc: Garry Dolley <gdolley@arpnetworks.com>,
Richard Hartmann <richih.mailinglist@gmail.com>,
git@vger.kernel.org
Subject: Re: Feedback outside of the user survey
Date: Mon, 20 Oct 2008 17:20:28 +0200 [thread overview]
Message-ID: <48FCA1BC.3060300@jaeger.mine.nu> (raw)
In-Reply-To: <48FC9D87.3010303@op5.se>
Andreas Ericsson wrote:
> Christian Jaeger wrote:
>> Andreas Ericsson wrote:
>>> Christian Jaeger wrote:
>>>> If you really wanted, I suppose you could additionally look into
>>>> implementing a kind of shallow cloning that only copies objects
>>>> over the wire which are necessary for representing the subdirectory
>>>> you're interested in.
>>>>
>>>
>>> So what do you do when one such commit also affects something outside
>>> the subdirectory?
>>
>> You haven't said what you mean with "affect".
>>
>
> I mean "how would you handle a commit (and its tree-object) that updates
> all Makefiles in, for example, the Linux kernel project?". Those files
> are spread far and wide, and you'd want that change to *your* tree, but
> getting it into your tree either means you need to rewrite the tree (and
> thereby the commit) itself to get rid of uninteresting blob's from the
> tree, and you'd also have to prune the tree to not reveal the directory
> layout of the rest of the repository.
You have said "either" but not "or".
> I take it parentage could be resolved by a ridiculously large
> grafts-file.
Hm, not sure whether you mean to rescue the situation with rewritten
commits here -- but hell no, I certainly don't mean to have different
commit objects for different clones/checkouts.
> What you'd end up with wouldn't be a git repository at all anymore. It
> would be a "stump", as it'd be missing large parts of the tree entirely.
That was my point, yes.
> I'm unsure just how much you'd have to compute to be able to use such a
> stump to incorporate your changes with other users again, but I doubt it
> would be trivial to implement. Good thing it's not my itch, really.
I've been suggesting it to Garry :)
Maybe whoever writes up something on the wiki regarding subdirectory
checkouts in SVN versus Git could still care about what the "fundamental
technical" limits are versus what the current implementation (or
practicalness) imposes. It will be both a more enlightening and
potentially more future-proof explanation then.
Christian.
next prev parent reply other threads:[~2008-10-20 15:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 10:19 Feedback outside of the user survey Richard Hartmann
2008-10-16 10:28 ` Jeff King
2008-10-16 11:08 ` Richard Hartmann
2008-10-16 11:56 ` Garry Dolley
2008-10-16 13:18 ` Richard Hartmann
2008-10-16 20:32 ` Christian Jaeger
2008-10-18 13:49 ` Garry Dolley
2008-10-18 14:01 ` Christian Jaeger
2008-10-20 9:57 ` Andreas Ericsson
2008-10-20 14:43 ` Christian Jaeger
2008-10-20 15:02 ` Andreas Ericsson
2008-10-20 15:20 ` Christian Jaeger [this message]
2008-10-20 16:11 ` Andreas Ericsson
2008-10-20 16:57 ` Christian Jaeger
2008-10-20 17:30 ` Christian Jaeger
2008-10-20 22:41 ` Junio C Hamano
2008-10-21 7:24 ` Christian Jaeger
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=48FCA1BC.3060300@jaeger.mine.nu \
--to=christian@jaeger.mine.nu \
--cc=ae@op5.se \
--cc=gdolley@arpnetworks.com \
--cc=git@vger.kernel.org \
--cc=richih.mailinglist@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).