Re: Core and Not-So Core

[Jon Seymour <jon.seymour@gmail.com>]

>
> > I think it would be worthwhile if care was taken to draw a distinction
> > between the repository and the cache aspects of the git core, perhaps
> > even going to the extreme of moving all knowledge of the  cache into
> > cogito itself. By clearly drawing this distinction, we will more
> > easily enable the creation of different kind of tools sets atop the
> > foundation of the GIT repository format.
>
> I think this is nonsensical. The cache format is tied to the way in which
> the repository accessing code is written, so a git-core separate from the
> cache wouldn't have a useful set of code.
>

I guess I agree it is somewhat nonsensical if one considers the
current git toolset as a collection of programs - the exercise now
might simply reduce to classifying git tools as
index-using/non-index-using and nothing more. However, it might be
worth keeping in mind when/if the "libification" of git happens so
that there is a clean separation of layers in the API between the
repository API and index/cache/workspace API.

> It might be worthwhile to produce a separate document describing the
> repository format, such that it could be accessed by different code,
> however. Of course, the index file wouldn't be part of this documentation,
> for the same reason that the public git repositories don't include index
> files.
>

And thanks for your constructive criticism.

jon.
--
homepage: http://www.zeta.org.au/~jon/
blog: http://orwelliantremors.blogspot.com/