git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Ian Hilt <ian.hilt@gmail.com>
Cc: git@vger.kernel.org, Kevin Ballard <kevin@sb.org>
Subject: Re: [PATCH] Rephrased git-describe description
Date: Wed, 14 May 2008 11:46:45 -0700	[thread overview]
Message-ID: <7v7idwoh9m.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1210789855-29413-1-git-send-email-ian.hilt@gmail.com> (Ian Hilt's message of "Wed, 14 May 2008 14:30:55 -0400")

Ian Hilt <ian.hilt@gmail.com> writes:

> git-describe: Make description more readable.

Thanks, both.  I think the above is meant to be on the Subject: line, and
the text certainly is more readable.

> Signed-off-by: Ian Hilt <ian.hilt@gmail.com>
> ---
>  Documentation/git-describe.txt |    7 ++++---
>  1 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/git-describe.txt b/Documentation/git-describe.txt
> index d9aa2f2..69e1ab7 100644
> --- a/Documentation/git-describe.txt
> +++ b/Documentation/git-describe.txt
> @@ -13,9 +13,10 @@ SYNOPSIS
>  DESCRIPTION
>  -----------
>  The command finds the most recent tag that is reachable from a
> -commit, and if the commit itself is pointed at by the tag, shows
> -the tag.  Otherwise, it suffixes the tag name with the number of
> -additional commits and the abbreviated object name of the commit.
> +commit.  If the tag points to the commit, then only the tag is
> +shown.  Otherwise, it suffixes the tag name with the number of
> +additional commits on top of the tagged object and the
> +abbreviated object name of the most recent commit.

  reply	other threads:[~2008-05-14 18:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14 18:30 [PATCH] Rephrased git-describe description Ian Hilt
2008-05-14 18:46 ` Junio C Hamano [this message]
2008-05-14 20:01   ` Dirk Süsserott
2008-05-14 23:02   ` Ian Hilt
2008-05-17  0:03     ` Junio C Hamano
  -- strict thread matches above, loose matches on Subject: below --
2008-05-14 14:22 Ian Hilt
2008-05-14 16:57 ` Kevin Ballard
2008-05-14 18:00   ` Ian Hilt
2008-05-14 18:03     ` Kevin Ballard

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=7v7idwoh9m.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=ian.hilt@gmail.com \
    --cc=kevin@sb.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).