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

for-each-ref output order change in 2.7.0

From
Bryan Turner <bturner@atlassian.com>
Date
Jan 9, 2016, 01:07 UTC
Message-ID
<CAGyf7-FSP3Z7HO=LpoQck8q9sSj3fGYCx1=gNa6fXEkovxAxHw@mail.gmail.com>

In one of our tests, we have a set of branches whose names are all special characters (%, @, etc). Most of them branches have identical tip commits and just have different names. In 2.7.0, when ordering by -committerdate, the branches are now returned in a different order. I don't think this is a bug, based on the commit it bisects to, but I'm wondering if someone can confirm.

2.6.5 and prior (tested all the way back to 1.7.6, so this was consistent for a long time):

refs/heads/!@#% -> Tue Jan 3 17:04:06 2012 +1100 refs/heads/!@#$% -> Tue Jan 3 17:00:51 2012 +1100 refs/heads/% -> Tue Jan 3 17:00:51 2012 +1100 refs/heads/@#$% -> Tue Jan 3 17:00:51 2012 +1100 refs/heads/@#% -> Tue Jan 3 17:00:51 2012 +1100

2.7.0:

refs/heads/!@#% -> Tue Jan 3 17:04:06 2012 +1100 refs/heads/@#% -> Tue Jan 3 17:00:51 2012 +1100 refs/heads/@#$% -> Tue Jan 3 17:00:51 2012 +1100 refs/heads/% -> Tue Jan 3 17:00:51 2012 +1100 refs/heads/!@#$% -> Tue Jan 3 17:00:51 2012 +1100

I've bisected this back to:
bturner@ubuntu:~/Development/oss/git/git$ git bisect bad
9e468334b41c1d1fc715de177ef1f61a36c1cf01 is the first bad commit
commit 9e468334b41c1d1fc715de177ef1f61a36c1cf01
Author: Karthik Nayak <karthik.188@gmail.com>
Date:   Fri Oct 30 14:15:28 2015 +0530
    ref-filter: fallback on alphabetical comparison

The message for that commit indicates that sorting numerics (which I assume is the implementation for committerdate) now falls back on alphabetical for identical values, suggesting this order change is actually intentional and correct. Is that right?

(Note: The alphabetical-ness of the branch names is reversed, which seems logical given my original sort was -committerdate. A --sort=refname looks like this.

refs/heads/!@#$% -> Tue Jan 3 17:00:51 2012 +1100 refs/heads/!@#% -> Tue Jan 3 17:04:06 2012 +1100 refs/heads/% -> Tue Jan 3 17:00:51 2012 +1100 refs/heads/@#$% - >Tue Jan 3 17:00:51 2012 +1100 refs/heads/@#% -> Tue Jan 3 17:00:51 2012 +1100

That's probably more correct too.)

Best regards, Bryan Turner

Next: Matthieu Moy
Message 1 of 6 in “for-each-ref output order change in 2.7.0”
  1. Bryan TurnerJan 9, 2016
  2. Matthieu MoyJan 9, 2016
  3. Karthik NayakJan 9, 2016
  4. Johannes SixtJan 9, 2016
  5. Karthik NayakJan 9, 2016
  6. Johannes SixtJan 10, 2016

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.