From: Phillip Wood <phillip.wood123@gmail.com>
Date: Fri, 28 Feb 2025 10:59:44 GMT
Subject: Re: 'git rev-list' commit ordering issue
Message-ID: <d7b1416d-d201-400e-a0eb-b9e526f740ab@gmail.com>
In-Reply-To: <CABXAcUwHd2Rr8iOZ7F2k5DGiBNH87pwG3oyRWLrP40=MgD91-w@mail.gmail.com>

Hi Clement

On 26/02/2025 22:30, Clement Moyroud wrote:
> On Wed, Feb 26, 2025 at 10:58 AM D. Ben Knoble <ben.knoble@gmail.com> wrote:
 >
>> Is `--topo-order` of no help here?
> 
> Unfortunately no, because it'll look at the ancestors. I get more
> commits (400k+ extra
> commits in my real world case) than I have on stdin:
> $ git log -1 --pretty=%H 2025.2 | git rev-list --stdin --topo-order --count
> 417776

This seems to have lost "--no-walk".

     ... | git rev-list --stdin --topo-order --no-walk

should list only the commits passed on stdin in topographic order I think.

Best Wishes

Phillip

> --
> Clement
> 
>>
>>>
>>> Below is the system info gathered by `git bugreport`.
>>>
>>> Take care,
>>>
>>> Clement
>>>
>>>
>>> [System Info]
>>> git version:
>>> git version 2.48.1
>>> cpu: x86_64
>>> no commit associated with this build
>>> sizeof-long: 8
>>> sizeof-size_t: 8
>>> shell-path: /bin/sh
>>> libcurl: 7.87.0
>>> OpenSSL: OpenSSL 1.0.1e-fips 11 Feb 2013
>>> zlib: 1.2.3
>>> uname: Linux 4.18.0-553.33.1.el8_10.x86_64 #1 SMP Thu Dec 19 14:28:01
>>> UTC 2024 x86_64
>>> compiler info: gnuc: 6.2
>>> libc info: glibc: 2.28
>>> $SHELL (typically, interactive shell): /bin/zsh
>>>
>>>
>>> [Enabled Hooks]
>>
>>
>>
>> --
>> D. Ben Knoble
>