From: Vincent van Ravesteijn <vfr@lyx.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: [PATCH 1/2] Unification of user message strings
Date: Tue, 20 Mar 2012 08:47:46 +0100 [thread overview]
Message-ID: <4F683622.6010409@lyx.org> (raw)
In-Reply-To: <7vaa3c9ste.fsf@alter.siamese.dyndns.org>
> I had a vague impression that plumbing messages tend to be lowercase. If
> it is not be too much trouble, it might be interesting to redo the numbers
> divided into the plumbing and Porcelain messages. Perhaps these "50%"
> folks updated both plumbing and Porcelain. Another possibility is that
> they tried to follow the local convention when they added a new one, or
> reworded an existing one.
>
> If we would be rewording, we would only be doing the Porcelain messages,
> so I am OK with either way.
It seems that the terms "Porcelain" and "plumbing" seems to be mixed up
somewhere.
From 'git help status': "The porcelain format is similar to the short
format, but is guaranteed not to change in a backwards-incompatible way
between git versions or based on user configuration. This makes it ideal
for parsing by scripts".
From 'http://progit.org/book/ch9-1.html': "....it has a bunch of verbs
that do low-level work and were designed to be chained together UNIX
style or called from scripts. These commands are generally referred to
as “plumbing” commands, and the more user-friendly commands are called
“porcelain” commands."
It feels like 'porcelain' means: "be careful, things break easily"; and
'plumbing' means: "use all the force you want to get it into (a
user-friendly) shape".
Second, to me it is not totally clear which strings are plumbing and
which ones are porcelain. Is there a general rule to tell ? The
command-list file says what the general intention of a command is, but
often it's both plumbing as porcelain.
Can anyone help me out here ?
Vincent
next prev parent reply other threads:[~2012-03-20 7:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 17:51 [PATCH 0/2] Unify the style of user messages Vincent van Ravesteijn
2012-03-19 17:51 ` [PATCH 1/2] Unification of user message strings Vincent van Ravesteijn
2012-03-19 19:39 ` Junio C Hamano
2012-03-19 20:16 ` Vincent van Ravesteijn
2012-03-19 20:53 ` Jeff King
2012-03-19 21:36 ` Junio C Hamano
2012-03-20 7:47 ` Vincent van Ravesteijn [this message]
2012-03-20 12:01 ` Jakub Narebski
2012-03-20 12:33 ` Vincent van Ravesteijn
2012-03-19 17:51 ` [PATCH 2/2] Make some strings translatable Vincent van Ravesteijn
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=4F683622.6010409@lyx.org \
--to=vfr@lyx.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.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).