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 15:36:42 -0800 [thread overview]
Message-ID: <7vps9aeghh.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0701191729060.3011@xanadu.home> (Nicolas Pitre's message of "Fri, 19 Jan 2007 17:44:58 -0500 (EST)")
Nicolas Pitre <nico@cam.org> writes:
> I don't think fsck-objects is really plumbing though. I'd tag it as
> ancillaryinterrogators.
>
> Also, having:
>
> git-am(1)
> Apply a series of patches from a mailbox.
>
> git-applymbox(1)
> Apply a series of patches in a mailbox.
>
> looks a bit weird.
I thought about that issue (also annotate vs blame). I'm fine
with demoting applymbox to ancillary, perhaps with potential
future deprecation in mind (but that would be a separate topic).
annotate is already ancillary and blame also is. Do you want to
promote one of them to mainporcelain?
> Is git-show-branch really a primary command?
Ah, I didn't notice that you wanted to move it out of
mainporcelain in your patch.
I personally use it quite often while juggling topics,
especially since I do not usually work inside X, but I'm fine
either way -- ancillaryinterrogators?
> I'd just drop the "to put it another way" entirely.
Ok, then how about this on top of what you saw on the list.
diff --git a/Documentation/cmd-list.perl b/Documentation/cmd-list.perl
index 9443ab3..4b76d19 100755
--- a/Documentation/cmd-list.perl
+++ b/Documentation/cmd-list.perl
@@ -62,7 +62,7 @@ __DATA__
git-add mainporcelain
git-am mainporcelain
git-annotate ancillaryinterrogators
-git-applymbox mainporcelain
+git-applymbox ancillaryinterrogators
git-applypatch purehelpers
git-apply plumbingmanipulators
git-archimport foreignscminterface
@@ -159,7 +159,7 @@ git-send-pack synchingrepositories
git-shell synchelpers
git-shortlog mainporcelain
git-show mainporcelain
-git-show-branch mainporcelain
+git-show-branch ancillaryinterrogators
git-show-index plumbinginterrogators
git-show-ref plumbinginterrogators
git-sh-setup purehelpers
diff --git a/Documentation/git.txt b/Documentation/git.txt
index ded48b5..9761de3 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -115,9 +115,9 @@ gitlink:git-read-tree[1].
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.
+primarily for scripted use. The interface to Porcelain commands
+on the other hand are subject to change in order to improve the
+end user experience.
The following description divides
the low-level commands into commands that manipulate objects (in
next prev parent reply other threads:[~2007-01-19 23:36 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
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 [this message]
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=7vps9aeghh.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.