From: Junio C Hamano <gitster@pobox.com>
To: Harald Nordgren <haraldnordgren@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] ls-remote: create '--sort' option
Date: Mon, 02 Apr 2018 13:12:39 -0700 [thread overview]
Message-ID: <xmqq1sfxz7t4.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20180402200736.80161-1-haraldnordgren@gmail.com> (Harald Nordgren's message of "Mon, 2 Apr 2018 22:07:36 +0200")
Harald Nordgren <haraldnordgren@gmail.com> writes:
> Subject: Re: [PATCH] ls-remote: create '--sort' option
It would be more helpful to mark as [PATCH v2] a rerolled patch like
this.
> Create a '--sort' option for ls-remote. This is useful e.g. for the Go
> repository after the release of version 1.10, where by default v1.10 is
> sorted before v1.2. See:
>
> $ git ls-remote -t https://go.googlesource.com/go
Does this sample command line also need updating for the refined
design?
> ...
> 205f850ceacfc39d1e9d76a9569416284594ce8c refs/tags/go1.1
> d260448f6b6ac10efe4ae7f6dfe944e72bc2a676 refs/tags/go1.1.1
> 1d6d8fca241bb611af51e265c1b5a2e9ae904702 refs/tags/go1.1.2
> bf86aec25972f3a100c3aa58a6abcbcc35bdea49 refs/tags/go1.10
> ac7c0ee26dda18076d5f6c151d8f920b43340ae3 refs/tags/go1.10.1
> ...
> + git ls-remote --sort="-version:refname" --tags self >actual &&
> + test_cmp expect actual
> +...
> + git ls-remote --sort="-refname" --tags self >actual &&
These both look sensible (also the variant without the dash prefix
which I omitted from the quote).
next prev parent reply other threads:[~2018-04-02 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[PATCH] ls-remote: create option to sort by versions>
2018-04-02 3:23 ` [PATCH 2/2] ls-remote: create option to sort by versions Harald Nordgren
2018-04-02 20:07 ` [PATCH] ls-remote: create '--sort' option Harald Nordgren
2018-04-02 20:12 ` Junio C Hamano [this message]
2018-04-02 21:14 ` Harald Nordgren
2018-04-02 21:19 ` Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq1sfxz7t4.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=haraldnordgren@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).