Re: Features from GitSurvey 2010

Nguyen Thai Ngoc Duy [off-list ref] writes:

On Tue, Feb 1, 2011 at 11:27 PM, Shawn Pearce [off-list ref] wrote:
...

quoted

I think Junio has already started thinking about this one.

I need to get nd/pathspec right and implement negative pathspecs
before returning to this feature.

I don't think we need negative pathspecs before going forward.

I wanted a unified "We have a path; is it inside this set of pathspecs?"
(and its sibling, "We have a leading path and a name_entry taken from that
tree; is it inside this set of pathspecs?"), and with that we can run:

	$ git clone git://k.org/pub/scm/git/git.git -- Documentation '*.sh'

that would limit the clone (not just checkout) to the given parts of the
tree.  By recording the pathspecs in the repository (and initially making
it frozen---we can design extending the scope in later rounds), we can
limit "fsck", "unpack-trees", "log", etc. all using the unified pathspec
API.

We may later want to add negative or imaginary pathspecs to the mix, but
as long as the unified pathspec API understands that, the narrow-clone
part should be able to be unaware of that.

So I think that is (or at least _should be_ if the pathspec API is done
right) pretty much orthogonal.