From: Junio C Hamano <junkio@cox.net>
To: Nicolas Pitre <nico@cam.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation/git.txt: command re-classification
Date: Fri, 19 Jan 2007 14:22:17 -0800 [thread overview]
Message-ID: <7vbqkufyhy.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0701191437450.3011@xanadu.home> (Nicolas Pitre's message of "Fri, 19 Jan 2007 17:08:53 -0500 (EST)")
Nicolas Pitre <nico@cam.org> writes:
> OK. But I think the following are still misclassified:
>
> git-rev-parse
> git-runstatus
> git-fsck-objects
Thanks for proofreading. runstatus should be a pure helper. I
am not sure what rev-parse and fsck-objects are, but they are
not primary porcelain. rev-parse could sit next to rev-list and
fsck-objects, I guess.
>> +The interface (input, output, set of options and the semantics)
>> +to these low-level commands are meant to be a lot more stable
>> +than Porcelain level commands, because these commands are
>> +primarily for scripted use. To put it another way, the
>> +interface to Plumbing commands are subject to change in order to
>> +improve the end user experience.
>
> I think the "to put it another way" sentence is a bit confusing here.
I agree. What I wanted to say was the interface to plumbing is
sacred and we will not lightly change it without a very good
reason, while Porcelains are more or less "for breaking".
Better wording is certainly appreciated.
next prev parent reply other threads:[~2007-01-19 22:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 22:25 [PATCH] Documentation: revisit command qualification in git.txt Nicolas Pitre
2007-01-19 6:32 ` [PATCH] Documentation/git.txt: command re-classification Junio C Hamano
2007-01-19 22:08 ` Nicolas Pitre
2007-01-19 22:18 ` Jakub Narebski
2007-01-19 22:22 ` Junio C Hamano [this message]
2007-01-19 22:44 ` Nicolas Pitre
2007-01-19 22:57 ` Jakub Narebski
2007-01-19 22:59 ` J. Bruce Fields
2007-01-19 23:36 ` Junio C Hamano
2007-01-20 1:44 ` Nicolas Pitre
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=7vbqkufyhy.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=nico@cam.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.