git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Bryan Larsen <bryan.larsen@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git, porcelain, darcs, and version 1.0
Date: Mon, 18 Jul 2005 12:11:25 -0700	[thread overview]
Message-ID: <7vslycnd42.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 42DB341D.6050506@gmail.com

Bryan Larsen <bryan.larsen@gmail.com> writes:

> ... 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.

> 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".

  reply	other threads:[~2005-07-18 19:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-16 20:45 Darcs-Git: upgrading to Git 0.99 Juliusz Chroboczek
2005-07-17 10:40 ` [darcs-devel] " David Roundy
2005-07-18  4:46 ` git, porcelain, darcs, and version 1.0 Bryan Larsen
2005-07-18 19:11   ` Junio C Hamano [this message]
2005-07-18 20:18     ` Bryan Larsen
2005-07-18 19:49   ` Juliusz Chroboczek
2005-07-18 20:28     ` Bryan Larsen

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=7vslycnd42.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=bryan.larsen@gmail.com \
    --cc=git@vger.kernel.org \
    /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).