From: Junio C Hamano <gitster@pobox.com>
To: Christian Hesse <list@eworm.de>
Cc: Git Mailing List <git@vger.kernel.org>, Christian Hesse <mail@eworm.de>
Subject: Re: [PATCH 1/1] refs: update the version numbers...
Date: Tue, 16 Jul 2024 09:07:58 -0700 [thread overview]
Message-ID: <xmqqle219v6p.fsf@gitster.g> (raw)
In-Reply-To: <20240716095544.65931-1-list@eworm.de> (Christian Hesse's message of "Tue, 16 Jul 2024 11:55:44 +0200")
Christian Hesse <list@eworm.de> writes:
> From: Christian Hesse <mail@eworm.de>
>
> ... as they were one off.
>
> Signed-off-by: Christian Hesse <mail@eworm.de>
> ---
> refs.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/refs.h b/refs.h
> index 0ecba21b4a..b3e39bc257 100644
> --- a/refs.h
> +++ b/refs.h
> @@ -1087,10 +1087,10 @@ int repo_migrate_ref_storage_format(struct repository *repo,
> struct strbuf *err);
>
> /*
> - * The following functions have been removed in Git v2.45 in favor of functions
> + * The following functions have been removed in Git v2.46 in favor of functions
> * that receive a `ref_store` as parameter. The intent of this section is
> * merely to help patch authors of in-flight series to have a reference what
> - * they should be migrating to. The section will be removed in Git v2.46.
> + * they should be migrating to. The section will be removed in Git v2.47.
> */
> #if 0
> static char *resolve_refdup(const char *refname, int resolve_flags,
Right. "git blame" says this block came from c8f815c2 (refs: remove
functions without ref store, 2024-05-07), which is v2.46.0-rc0~119^2,
and will be published as part of v2.46, not v2.45.
Will queue. Thanks.
prev parent reply other threads:[~2024-07-16 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 9:55 [PATCH 1/1] refs: update the version numbers Christian Hesse
2024-07-16 16:07 ` Junio C Hamano [this message]
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=xmqqle219v6p.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=list@eworm.de \
--cc=mail@eworm.de \
/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.