Git development
 help / color / mirror / Atom feed
From: Mirko Faina <mroik@delayed.space>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Mirko Faina <mroik@delayed.space>
Subject: Re: What's cooking in git.git (Jun 2026, #04)
Date: Thu, 11 Jun 2026 18:40:21 +0200	[thread overview]
Message-ID: <airkGWlc69uVsVa8@exploit> (raw)
In-Reply-To: <xmqqmrx1oy9y.fsf@gitster.g>

On Thu, Jun 11, 2026 at 09:08:25AM -0700, Junio C Hamano wrote:
> * mf/revision-max-count-oldest (2026-05-18) 1 commit
>   (merged to 'next' on 2026-06-09 at 076600fa21)
>  + revision.c: implement --max-count-oldest
> 
>  "git rev-list" (and "git log" family of commands) learned a new "--max-count-oldest"
>  that picks oldest N commits in the range instead of the usual newest.
> 
>  Will merge to 'master'.
>  source: <xmqq4ijm3p2x.fsf@gitster.g>

Might want to wait and merge it in with [1].

[1] https://lore.kernel.org/git/a804828a046d8f12ef0d03eaf014807b079bb707.1781102091.git.mroik@delayed.space/

  reply	other threads:[~2026-06-11 16:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-11 16:08 What's cooking in git.git (Jun 2026, #04) Junio C Hamano
2026-06-11 16:40 ` Mirko Faina [this message]
2026-06-11 18:55   ` Junio C Hamano

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=airkGWlc69uVsVa8@exploit \
    --to=mroik@delayed.space \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox