Feature request - Subtree checkouts

Heya,

I'm trying to dig at various issues that are potential holdups for
migrating the Gentoo CVS tree into Git.

Since shallow checkouts are now available, there's just one more thing
that's missing: subtree checkouts. Not to be confused with sub-projects.

If the master tree has this as some example contents:
/foo
/abc/...
/bar/example
/bar/baz/some-content

We need to be able to check out arbitrary subtrees. So I might want to
check out everything (as the CVS administrator), while one of the more
focused developers just wants to check out /bar/baz/.

P.S. Does this list do some weird spam-blocking? I've tried 3 times now
to use git-send-email to send an unrelated minor patch set
(--subject-prefix for git-format-patch), and it has never shown up on
the list :-(.

-- 
Robin Hugh Johnson
Gentoo Linux Developer & Council Member
E-Mail     : robbat2@gentoo.org
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85

"Robin H. Johnson" [off-list ref] wrote:

P.S. Does this list do some weird spam-blocking? I've tried 3 times now
to use git-send-email to send an unrelated minor patch set
(--subject-prefix for git-format-patch), and it has never shown up on
the list :-(.

Yes.  It has cut down on our spam, but it has also caused some
things to be blocked, almost without good reason.  ;-)

I send a fair number of patches to this list (at times anyway) and
am also unable to use git-send-email.  If I have the email also CC
back to me it does make it through a number of SMTP server hops,
including my own spam filters, but it never makes it through the
Git mailing list.  So I dump the patches to an mbox with --stdout,
open them up in mutt and resend them there.  I've bound shift-G
to resend-message for that purpose...

-- 
Shawn.

Hi,

On Tue, 10 Apr 2007, Robin H. Johnson wrote:

Since shallow checkouts are now available, there's just one more thing 
that's missing: subtree checkouts. Not to be confused with sub-projects.

It should not be _that_ difficult. If I'm correct, it should touch exactly 
the same code as the commit v1.3.0~263^2~6 ("Assume unchanged" git).

ATM I have no time to do anything about it, so feel free to give it a try.

Ciao,
Dscho