From: Christian Couder <christian.couder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2024, #02; Thu, 7)
Date: Fri, 8 Mar 2024 11:31:41 +0100 [thread overview]
Message-ID: <CAP8UFD1oWrE-C0XYi47PrBF36bJzHAv-jOq3r1UXw_BVnb97pA@mail.gmail.com> (raw)
In-Reply-To: <xmqqplw5ihm7.fsf@gitster.g>
(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.
> source: <20240214142513.4002639-1-christian.couder@gmail.com>
next prev parent reply other threads:[~2024-03-08 10:31 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 [this message]
2024-03-08 15:37 ` Junio C Hamano
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=CAP8UFD1oWrE-C0XYi47PrBF36bJzHAv-jOq3r1UXw_BVnb97pA@mail.gmail.com \
--to=christian.couder@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).