From: Bryan Larsen <bryan.larsen@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Barebone Porcelain. Where to stop?
Date: Mon, 18 Jul 2005 00:41:21 -0400 [thread overview]
Message-ID: <42DB32F1.5020900@gmail.com> (raw)
In-Reply-To: <7vek9yirdi.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> I have been somewhat disturbed and confused by the fact that the
> line between what Porcelain like Cogito does and what we ship as
> part of "core GIT" is getting more and more blurred. This was
> especially so while I was working on the $GIT_DIR/branches/
> patch.
I have also been disturbed. But I am gratified that such a core git
personage shares my concern. This is enough from a technical point of
view, at least for me.
Any lack of porcelain momentum is probably due to git having better
documentation than the current porcelains, such as cogito and stacked
git. The documentation, like tutorial.txt and Jeff Garzik's git kernel
howto give the impression that most kernel folks use git instead of cogito.
I personally think that the cogito interface and stacked git interfaces
are much nicer than git's, and would like to see these two tools achieve
some momentum.
Another way of encouraging porcelain is by helping Pasky and Catalin
out. Myself, I have been sending corresponding patches for Cogito and
Stacked when making changes to git. This is purely selfish: I use both
of these porcelains, but if it became general practice, we'd probably
see less breakage.
Bryan
next prev parent reply other threads:[~2005-07-18 4:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-16 17:37 Barebone Porcelain. Where to stop? Junio C Hamano
2005-07-18 4:41 ` Bryan Larsen [this message]
2005-07-18 10:22 ` Catalin Marinas
2005-07-18 18:59 ` Junio C Hamano
2005-07-18 20:57 ` Frank Sorenson
2005-07-19 0:10 ` Junio C Hamano
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=42DB32F1.5020900@gmail.com \
--to=bryan.larsen@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).