git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] tag: support mixing --sort=<spec> and -n

From
Karthik Nayak <karthik.188@gmail.com>
Date
Sep 6, 2015, 03:52 UTC
Message-ID
<CAOLa=ZTiG8aMdURDYTHALGfhkg_YWe6bXEmPUySgGBrrQXD+Nw@mail.gmail.com>
In-Reply-To
<CA+P7+xo=4mC0fKkbtL+fkMXGxdUNcdUGUYHdaJ58MF9jVUUziw@mail.gmail.com>
On Sun, Sep 6, 2015 at 3:55 AM, Jacob Keller <jacob.keller@gmail.com> wrote:
Show 16 quoted lines
> On Sat, Sep 5, 2015 at 10:52 AM, Rudy Matela <rudy@matela.com.br> wrote:
>>
>> Allow -n and --sort=version:refname to be used together
>> instead of failing with:
>>
>>   fatal: --sort and -n are incompatible
>>
>> Signed-off-by: Rudy Matela <rudy@matela.com.br>
>
> Nice! I've been wondering about this one for a while. Especially since
> implementing tag.sort configuration which made -n not work at all.
>
> Note that it may be worth rebasing this on top of Karthik's part tag
> to use ref-filter series, since I think there will be plenty of merge
> conflicts there...
>

Its already resolved in my series. We use ref-filter's sorting APIs there :)

-- 
Regards,
Karthik Nayak
Previous: Jacob KellerNext: Junio C Hamano
Message 3 of 5 in “tag: support mixing --sort=<spec> and -n”
  1. tag: support mixing --sort=<spec> and -nRudy Matela, Sep 5, 2015
  2. Jacob KellerSep 5, 2015
  3. Karthik NayakSep 6, 2015
  4. Junio C HamanoSep 6, 2015
  5. Jacob KellerSep 6, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.