All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2024, #02; Thu, 7)
Date: Fri, 08 Mar 2024 07:37:16 -0800	[thread overview]
Message-ID: <xmqqy1ashh03.fsf@gitster.g> (raw)
In-Reply-To: <CAP8UFD1oWrE-C0XYi47PrBF36bJzHAv-jOq3r1UXw_BVnb97pA@mail.gmail.com> (Christian Couder's message of "Fri, 8 Mar 2024 11:31:41 +0100")

Christian Couder <christian.couder@gmail.com> writes:

> (Sorry for sending this first privately to Junio by mistake.)
>
> On Fri, Mar 8, 2024 at 3:27 AM Junio C Hamano <gitster@pobox.com> wrote:
>
>> * cc/rev-list-allow-missing-tips (2024-02-28) 5 commits
>>   (merged to 'next' on 2024-03-01 at fd7b109d04)
>>  + revision: fix --missing=[print|allow*] for annotated tags
>>   (merged to 'next' on 2024-03-01 at ac0fc94378)
>>  + rev-list: allow missing tips with --missing=[print|allow*]
>>  + t6022: fix 'test' style and 'even though' typo
>>  + oidset: refactor oidset_insert_from_set()
>>  + revision: clarify a 'return NULL' in get_reference()
>>
>>  Originally merged to 'next' on 2024-02-28
>>
>>  "git rev-list --missing=print" has learned to optionally take
>>  "--allow-missing-tips", which allows the objects at the starting
>>  points to be missing.
>
> The description might want to be updated as no new
> "--allow-missing-tips" option is introduced anymore. Maybe something
> like this instead:
>
> "git rev-list --missing=[print|allow*]" has learned to not die when
> some tips passed to it as command line arguments are missing. Instead
> those tips are just reported among the missing objects and ignored for
> traversal.

Thanks for a comment; better late than never.  We'd probably need to
update the release notes, as this is gone from the list of cooking
topics already.

  reply	other threads:[~2024-03-08 15:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08  2:26 What's cooking in git.git (Mar 2024, #02; Thu, 7) Junio C Hamano
2024-03-08 10:31 ` Christian Couder
2024-03-08 15:37   ` Junio C Hamano [this message]
2024-03-08 13:56 ` Phillip Wood
2024-03-08 15:42   ` Junio C Hamano
2024-03-09 11:34     ` Phillip Wood

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=xmqqy1ashh03.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.