From: Junio C Hamano Date: Tue, 28 Apr 2026 01:46:21 GMT Subject: Re: [PATCH v4 1/2] revision.c: implement -b-reverse=before for walks Message-ID: In-Reply-To: Mirko Faina writes: >> It might be that the right way to look at this new feature is not that >> "we are changing where reverse is applied", but "count limit is applied >> much later than usual" > > maybe --max-count-later as in max count is being applied later than > usual? (either way the users will still need to reach for the man pages > for clarifications). I very much more prefer what J6t suggested, which (if I am understanding him correctly) would make git log --max-count-oldest=3 $options conceptually run "git log" (without count limit but with other options like --grep, --author, --since, etc. applied) without showing anything until the last three commits remains, and then shows these last three commits. git log --max-count-oldest=3 --reverse $options would show these same last three commits, but in the order opposite to the first one.