From: Catalin Marinas <catalin.marinas@gmail.com>
To: Bryan Larsen <bryan.larsen@gmail.com>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: Barebone Porcelain. Where to stop?
Date: Mon, 18 Jul 2005 11:22:33 +0100 [thread overview]
Message-ID: <tnx3bqcxvkm.fsf@arm.com> (raw)
In-Reply-To: <42DB32F1.5020900@gmail.com> (Bryan Larsen's message of "Mon, 18 Jul 2005 00:41:21 -0400")
Bryan Larsen <bryan.larsen@gmail.com> wrote:
> 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.
I don't see git going towards stgit at all. Indeed, it gets closer to
cogito but I still like cogito over plain git since it's easier to use
(my goal, though, is to add pull/clone commands to stgit so that one
doesn't need to rely on directly using other tools).
I am aware that, probably, the biggest problem with stgit is the
documentation (and also a lack of regression tests). I hope I will
find some time soon to write a tutorial and improve the command line
help. I will setup a wiki in the next few days so that others can
easily fix/update the documentation.
--
Catalin
next prev parent reply other threads:[~2005-07-18 10:23 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
2005-07-18 10:22 ` Catalin Marinas [this message]
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=tnx3bqcxvkm.fsf@arm.com \
--to=catalin.marinas@gmail.com \
--cc=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).