public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: Junio C Hamano <gitster@pobox•com>
To: Michael Haggerty <mhagger@alum•mit.edu>
Cc: git@vger•kernel.org, "Nguyễn Thái Ngọc Duy" <pclouds@gmail•com>
Subject: Re: [PATCH 2/5] git tag: mention versionsort.prereleaseSuffix in manpage
Date: Thu, 23 Apr 2015 11:28:55 -0700	[thread overview]
Message-ID: <xmqqr3ra3di0.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1429792070-22991-3-git-send-email-mhagger@alum.mit.edu> (Michael Haggerty's message of "Thu, 23 Apr 2015 14:27:47 +0200")

Michael Haggerty <mhagger@alum•mit.edu> writes:

> Signed-off-by: Michael Haggerty <mhagger@alum•mit.edu>
> ---

Makes sense; will queue on nd/versioncmp-prereleases.

Thanks.

>  Documentation/git-tag.txt | 11 +++++++----
>  1 file changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/git-tag.txt b/Documentation/git-tag.txt
> index bfba4ef..f5b267e 100644
> --- a/Documentation/git-tag.txt
> +++ b/Documentation/git-tag.txt
> @@ -98,10 +98,13 @@ OPTIONS
>  --sort=<type>::
>  	Sort in a specific order. Supported type is "refname"
>  	(lexicographic order), "version:refname" or "v:refname" (tag
> -	names are treated as versions). Prepend "-" to reverse sort
> -	order. When this option is not given, the sort order defaults to the
> -	value configured for the 'tag.sort' variable if it exists, or
> -	lexicographic order otherwise. See linkgit:git-config[1].
> +	names are treated as versions). The "version:refname" sort
> +	order can also be affected by the
> +	"versionsort.prereleaseSuffix" configuration variable. Prepend
> +	"-" to reverse sort order. When this option is not given, the
> +	sort order defaults to the value configured for the 'tag.sort'
> +	variable if it exists, or lexicographic order otherwise. See
> +	linkgit:git-config[1].
>  
>  --column[=<options>]::
>  --no-column::

next prev parent reply	other threads:[~2015-04-23 18:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23 12:27 [PATCH 0/5] Tweak the 2.4.0 release notes and related docs Michael Haggerty
2015-04-23 12:27 ` [PATCH 1/5] status: document the -v/--verbose option Michael Haggerty
2015-04-23 18:26   ` Junio C Hamano
2015-04-23 12:27 ` [PATCH 2/5] git tag: mention versionsort.prereleaseSuffix in manpage Michael Haggerty
2015-04-23 18:28   ` Junio C Hamano [this message]
2015-04-23 12:27 ` [PATCH 3/5] RelNotes: correct name of versionsort.prereleaseSuffix Michael Haggerty
2015-04-23 18:29   ` Junio C Hamano
2015-04-23 12:27 ` [PATCH 4/5] RelNotes: refer to the rebase -i "todo list", not "insn sheet" Michael Haggerty
2015-04-23 12:27 ` [PATCH 5/5] RelNotes: wordsmithing Michael Haggerty
2015-04-23 12:47   ` Michael Haggerty
2015-04-23 15:38     ` Junio C Hamano

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=xmqqr3ra3di0.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=mhagger@alum$(echo .)mit.edu \
    --cc=pclouds@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox