From: Thiago Farina <tfransosi@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation: Update the style of 'git-describe' command.
Date: Tue, 22 Sep 2009 21:24:58 -0400 [thread overview]
Message-ID: <a4c8a6d00909221824u617a9812j11af45b39e06c6d5@mail.gmail.com> (raw)
In-Reply-To: <7v3a6eo759.fsf@alter.siamese.dyndns.org>
On Tue, Sep 22, 2009 at 8:07 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Thiago Farina <tfransosi@gmail.com> writes:
>
>> $ git describe -h
>> -usage: git-describe [options] <committish>*
>> +usage: git describe [options] <commit-ish>*
>
> I think the first half of this line is correct but the other half is not.
>
> $ git grep --color -c -e committish -- Documentation/
> Documentation/git-describe.txt:6
> Documentation/git-fast-import.txt:8
> Documentation/git-name-rev.txt:1
> Documentation/git-shortlog.txt:1
> Documentation/gitcli.txt:1
> Documentation/howto/revert-branch-rebase.txt:1
>
> $ git grep --color -c -e commit-ish -- Documentation/
> Documentation/git-rebase.txt:1
> Documentation/git.txt:2
I did this:
git$ grep --color -n "commit-ish" *.c
builtin-revert.c:29: "git revert [options] <commit-ish>",
builtin-revert.c:34: "git cherry-pick [options] <commit-ish>",
builtin-send-pack.c:368: * (3) if both new and old are commit-ish,
and new is a
remote.c:1388: /* Both new and old must be commit-ish and new is descendant of
git$ grep --color -n "committish" *.c
builtin-describe.c:13: "git describe [options] <committish>*",
builtin-merge.c:885: * committish that is the same as HEAD there instead.
prev parent reply other threads:[~2009-09-23 1:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 23:48 [PATCH] Documentation: Update the style of 'git-describe' command Thiago Farina
2009-09-23 0:07 ` Junio C Hamano
2009-09-23 1:24 ` Thiago Farina [this message]
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=a4c8a6d00909221824u617a9812j11af45b39e06c6d5@mail.gmail.com \
--to=tfransosi@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).