Re: git, porcelain, darcs, and version 1.0
- From
Junio C Hamano <junkio@cox.net>
- Date
- Jul 18, 2005, 19:11 UTC
- Message-ID
- <7vslycnd42.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <42DB341D.6050506@gmail.com>
Bryan Larsen <bryan.larsen@gmail.com> writes:
Show 5 quoted lines
> ... Darcs and git work together to determine the minimal amount > that needs to go into libgit1.so. It gets blessed by being > documented, and doesn't change until libgit2.so. > > I'd like to see this added to Junio's list of "1.0" goals.
I should mention that I liked the libification work Brad Roberts did around late April. Unfortunately the things have been always in great flux for the last couple of months, and it was too hard to include that and maintain it back then.
I fully agree that supporting C-level linkage is worthy, and should be one of our longer term goals.
Show 5 quoted lines
> A similar 1.0 goal would be to document porcelain's use of the .git > directory. For instance, stacked git uses .git/patches, > .git/patchdescr.tmpl and .git/patchexport.tmpl. If Linus does not > accept a patch documenting this usage, stacked git should use .stgit > instead.
I agree that coordinating the namespace under $GIT_DIR among Porcelains is something we need (it was what prompted me to steal the branches/ convention from Cogito). The job of the core should be to help Porcelains avoid stepping on each other's toes.
The documentation of the internals for $GIT_DIR/patches is probably better left to StGIT documentation, though, at the moment. When other Porcelains start wishing to access the "series of patches expressed as a set of commit chain" expressed by StGIT there (e.g. show patch series in addition to regular commit chain in gitk), the core should help the Porcelains to work well with each other, to do things in a compatible way. This may involve moving some common things to core side and mention the convention for Porcelains to work well together in the core documentation.
However, I am slightly negative about suggesting these two to be part of the 1.0 goals. Linus wanted to make 1.0 how many weeks ago? I personally think that a usable baseline, stable enough to allow stripping out the core part currently shipped as part of Cogito, would be a good place to stop and declare 1.0. My list was meant to enumuerate what might be missing from the "usable baseline".