From: "Shawn O. Pearce" <spearce@spearce.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Daniel Barkalow <barkalow@iabervon.org>,
"Randal L. Schwartz" <merlyn@stonehenge.com>,
Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>,
git@vger.kernel.org
Subject: Re: Many gits are offline this week
Date: Sun, 7 Oct 2007 19:09:53 -0400 [thread overview]
Message-ID: <20071007230953.GC2137@spearce.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0710072331050.4174@racer.site>
Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> On Sun, 7 Oct 2007, Daniel Barkalow wrote:
>
> > For that matter, gitweb is essentially a limited porcelain. And this
> > points out that all VCSes have alternative porcelains, but git is
> > unusual in having convenient plumbing to support and encourage this.
>
> I do not consider viewers "porcelain". And gitweb is essentially just a
> viewer.
So you don't consider gitk to be porcelain? I do. The plumbing
output of git-rev-list is uh, ugly. gitk may still not be the best
looking application on the internet but it sure beats looking at
rev-list output by eye.
Porcelain is really anything that calls plumbing to make the task
of invoking or processing the output of plumbing easier on the
human using it. That's it. Obviously you can work Git by just the
plumbing. Just like you can compute SHA-1 by hand. You just choose
not to as the time it would take is more than you want to invest.
Or have left in this mortal existance...
I almost always forget about the web interfaces. There's a number
of them and I don't use them often enough to really think about it.
I don't know why I always forget about them. I never forget about
StGit or qgit, and yet I never use those either...
--
Shawn.
next prev parent reply other threads:[~2007-10-07 23:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 1:04 Many gits are offline this week Shawn O. Pearce
2007-10-05 1:27 ` Randal L. Schwartz
2007-10-05 1:36 ` Johannes Schindelin
2007-10-05 1:43 ` Shawn O. Pearce
2007-10-05 1:59 ` alan
2007-10-05 9:14 ` Paolo Ciarrocchi
2007-10-05 13:12 ` Randal L. Schwartz
2007-10-05 14:41 ` Dmitry Potapov
2007-10-05 16:20 ` David Brown
2007-10-05 17:19 ` Dmitry Potapov
2007-10-05 18:33 ` Jeff King
2007-10-07 17:01 ` Shawn O. Pearce
2007-10-07 19:04 ` Daniel Barkalow
2007-10-07 22:31 ` Johannes Schindelin
2007-10-07 23:09 ` Shawn O. Pearce [this message]
2007-10-07 19:37 ` Randal L. Schwartz
2007-10-28 10:07 ` Mike Hommey
2007-10-05 1:43 ` Johannes Schindelin
2007-10-07 4:59 ` Steven Grimm
2007-10-05 15:13 ` Frank Lichtenheld
2007-10-05 20:26 ` Pierre Habouzit
2007-10-06 9:05 ` Lars Hjemli
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=20071007230953.GC2137@spearce.org \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.com \
--cc=paolo.ciarrocchi@gmail.com \
/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).