From: kristofferhaugsbakk@fastmail.com
To: git@vger.kernel.org
Cc: Kristoffer Haugsbakk <code@khaugsbakk.name>,
Patrick Steinhardt <ps@pks.im>
Subject: [PATCH 0/2] commit: remove deprecated functions
Date: Wed, 27 May 2026 15:59:24 +0200 [thread overview]
Message-ID: <CV_commit.h_remove_deprecated.714@msgid.xyz> (raw)
From: Kristoffer Haugsbakk <code@khaugsbakk.name>
Topic name: kh/commit-deprecated
Topic summary: Remove deprecated comments that were slated for removal
after Git 2.53.0.
See the comment:
/*
* Deprecated compatibility functions for `struct commit_list`, to be removed
* once Git 2.53 is released.
*/
I merged in `seen` and `next` yesterday and found no new in-flight usages
of these functions.
I commented on this patch but apparently it hasn’t hit any of these
integration branches yet:
Patch: replay: support replaying 2-parent merges
Link: https://lore.kernel.org/git/920cc022-8b63-4dbb-a41d-957ee01a5efd@app.fastmail.com/
[1/2] *: replace deprecated free_commit_list
[2/2] commit: remove deprecated functions
builtin/history.c | 4 ++--
commit.h | 19 -------------------
replay.c | 2 +-
upload-pack.c | 4 ++--
4 files changed, 5 insertions(+), 24 deletions(-)
base-commit: 56a4f3c3a221adf1df9b39da69b8a6890f803157
--
2.54.0.6.gf6fa7dd4140
next reply other threads:[~2026-05-27 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 13:59 kristofferhaugsbakk [this message]
2026-05-27 13:59 ` [PATCH 1/2] *: replace deprecated free_commit_list kristofferhaugsbakk
2026-05-28 5:24 ` Patrick Steinhardt
2026-05-28 6:49 ` Kristoffer Haugsbakk
2026-05-27 13:59 ` [PATCH 2/2] commit: remove deprecated functions kristofferhaugsbakk
2026-05-28 5:24 ` Patrick Steinhardt
2026-05-28 7:00 ` [PATCH v2 0/2] " kristofferhaugsbakk
2026-05-28 7:00 ` [PATCH v2 1/2] *: replace deprecated free_commit_list kristofferhaugsbakk
2026-05-28 7:00 ` [PATCH v2 2/2] commit: remove deprecated functions kristofferhaugsbakk
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=CV_commit.h_remove_deprecated.714@msgid.xyz \
--to=kristofferhaugsbakk@fastmail.com \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
/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