From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Jeff King <peff@peff.net>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"SZEDER Gábor" <szeder@ira.uka.de>,
"Matthieu Moy" <Matthieu.Moy@grenoble-inp.fr>,
"Sebastian Pipping" <webmaster@hartwork.org>,
"Git ML" <git@vger.kernel.org>
Subject: [PATCH] command-list.txt: mark git-archive plumbing
Date: Tue, 15 Feb 2011 14:04:26 +0700 [thread overview]
Message-ID: <20110215070426.GA6118@duynguyen-vnpc> (raw)
In-Reply-To: <20110209234621.GA12575@sigill.intra.peff.net>
The command's official status is porcelain. However by the nature of the
command it is frequently used in scripting and therefore its interface
must be strictly backward compatible.
Mark it plumbing to make it clear.
Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
---
On Wed, Feb 09, 2011 at 06:46:21PM -0500, Jeff King wrote:
> Obviously add and grep are the two that people have talked about. The
> archive behavior surprised me, and I would think it should be full-tree
> by default. But it is sort of plumbing-ish, in that people have probably
> scripted around and people _don't_ tend to create archives a lot. So it
> may fall into the same category as ls-files/ls-tree.
Perhaps a patch like this for the record?
command-list.txt | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/command-list.txt b/command-list.txt
index 95bf18c..7888121 100644
--- a/command-list.txt
+++ b/command-list.txt
@@ -5,7 +5,7 @@ git-am mainporcelain
git-annotate ancillaryinterrogators
git-apply plumbingmanipulators
git-archimport foreignscminterface
-git-archive mainporcelain
+git-archive mainporcelain plumbinginterrogators
git-bisect mainporcelain common
git-blame ancillaryinterrogators
git-branch mainporcelain common
--
1.7.3.1.256.g2539c.dirty
next prev parent reply other threads:[~2011-02-15 7:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 0:39 "git add -u" broken in git 1.7.4? Sebastian Pipping
2011-02-06 5:13 ` Jeff King
2011-02-06 19:35 ` Sebastian Pipping
2011-02-06 20:48 ` Matthieu Moy
2011-02-06 23:19 ` SZEDER Gábor
2011-02-06 23:49 ` Sebastian Pipping
2011-02-07 5:50 ` Junio C Hamano
2011-02-07 5:53 ` Jeff King
2011-02-07 6:46 ` Junio C Hamano
2011-02-07 7:29 ` Nguyen Thai Ngoc Duy
2011-02-07 18:34 ` SZEDER Gábor
2011-02-07 19:31 ` Junio C Hamano
2011-02-07 19:50 ` Jeff King
2011-02-08 10:05 ` SZEDER Gábor
2011-02-09 21:03 ` Jeff King
2011-02-09 22:40 ` Junio C Hamano
2011-02-09 23:46 ` Jeff King
2011-02-10 2:24 ` Nguyen Thai Ngoc Duy
2011-02-10 2:31 ` Jeff King
2011-02-10 2:46 ` Junio C Hamano
2011-02-10 7:46 ` Johannes Sixt
2011-02-10 8:13 ` Joshua Juran
2011-02-10 18:00 ` Matthieu Moy
2011-02-15 7:04 ` Nguyen Thai Ngoc Duy [this message]
2011-02-15 19:11 ` [PATCH] command-list.txt: mark git-archive plumbing Junio C Hamano
2011-02-16 9:32 ` Nguyen Thai Ngoc Duy
2011-02-07 20:57 ` "git add -u" broken in git 1.7.4? Matthieu Moy
2011-02-07 21:02 ` Jeff King
2011-02-07 21:49 ` Junio C Hamano
2011-02-08 1:25 ` Eric Raible
2011-02-08 2:16 ` Junio C Hamano
2011-02-07 6:48 ` Matthieu Moy
2011-02-07 8:27 ` Michael J Gruber
2011-02-07 11:15 ` SZEDER Gábor
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=20110215070426.GA6118@duynguyen-vnpc \
--to=pclouds@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=szeder@ira.uka.de \
--cc=webmaster@hartwork.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 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).