From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
"Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: Should git-citool be in mainporcelain in command-list?
Date: Mon, 6 Sep 2010 22:00:19 +0000 [thread overview]
Message-ID: <AANLkTimRoAgAtrkpyd08mVG93prQ40B1y=ReLRdNfbWt@mail.gmail.com> (raw)
In-Reply-To: <20100906213937.GF26371@burratino>
On Mon, Sep 6, 2010 at 21:39, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Ævar Arnfjörð Bjarmason wrote:
>
>> Maybe there should be an aliases category:
>>
>> $ grep -e git-gui -e citool command-list.txt
>> git-citool mainporcelain
>> git-gui mainporcelain
>>
>> A very minor nit, just something I ran into while gettext-izing and
>> wondered "what's that".
>>
>> But I'm probably the only one that's used command-list.txt for
>> anything non-Make related in a while :)
>
> Its main purpose is to populate the command list in git.1:
>
> Main porcelain commands
> [...]
> git-citool(1)
> Graphical alternative to git-commit.
> [...]
> git-gui(1)
> A portable graphical interface to Git.
>
> What do you think this should say? (Honest question --- I
> haven't thought hard about it.)
I haven't either, and I don't use git-gui or the git citool alias. I
didn't even know about it until yesterday.
The entries in git(1) don't indicate that citool is a convenience
alias for git-gui:
git-gui(1)
A portable graphical interface to Git.
git-citool(1)
Graphical alternative to git-commit.
Maybe it shouldn't be listed there at all to avoid confusion, or maybe
it should be in an aliases category to clearly indicate its function
as a convenience alias in the manpage.
next prev parent reply other threads:[~2010-09-06 22:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-06 21:27 Should git-citool be in mainporcelain in command-list? Ævar Arnfjörð Bjarmason
2010-09-06 21:39 ` Jonathan Nieder
2010-09-06 22:00 ` Ævar Arnfjörð Bjarmason [this message]
2010-09-06 22:07 ` Jonathan Nieder
2010-09-06 22:17 ` Ævar Arnfjörð Bjarmason
2010-09-06 22:31 ` Jonathan Nieder
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='AANLkTimRoAgAtrkpyd08mVG93prQ40B1y=ReLRdNfbWt@mail.gmail.com' \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=spearce@spearce.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).