From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2024, #05; Thu, 12)
Date: Mon, 16 Dec 2024 09:11:22 +0100 [thread overview]
Message-ID: <Z1_gqiCuTZOdRVO0@pks.im> (raw)
In-Reply-To: <xmqq8qslf5h1.fsf@gitster.g>
On Thu, Dec 12, 2024 at 09:31:06PM +0900, Junio C Hamano wrote:
> * ps/build-sign-compare (2024-12-06) 16 commits
> - t/helper: don't depend on implicit wraparound
> - scalar: address -Wsign-compare warnings
> - builtin/patch-id: fix type of `get_one_patchid()`
> - builtin/blame: fix type of `length` variable when emitting object ID
> - gpg-interface: address -Wsign-comparison warnings
> - daemon: fix type of `max_connections`
> - daemon: fix loops that have mismatching integer types
> - global: trivial conversions to fix `-Wsign-compare` warnings
> - pkt-line: fix -Wsign-compare warning on 32 bit platform
> - csum-file: fix -Wsign-compare warning on 32-bit platform
> - diff.h: fix index used to loop through unsigned integer
> - config.mak.dev: drop `-Wno-sign-compare`
> - global: mark code units that generate warnings with `-Wsign-compare`
> - compat/win32: fix -Wsign-compare warning in "wWinMain()"
> - compat/regex: explicitly ignore "-Wsign-compare" warnings
> - git-compat-util: introduce macros to disable "-Wsign-compare" warnings
>
> Start working to make the codebase buildable with -Wsign-compare.
>
> Will merge to 'next'?
> source: <20241206-pks-sign-compare-v4-0-0344c6dfb219@pks.im>
I think this series should be ready to go, yes.
> * ps/send-pack-unhide-error-in-atomic-push (2024-11-14) 2 commits
> - transport: don't ignore git-receive-pack(1) exit code on atomic push
> - t5504: modernize test by moving heredocs into test bodies
>
> "git push --atomic --porcelain" used to ignore failures from the
> other side, losing the error status from the child process, which
> has been corrected.
>
> Needs review.
> source: <20241113-pks-push-atomic-respect-exit-code-v1-0-7965f01e7f4e@pks.im>
There was a newer version of this series again sent by Jiang Xin. I'll
try to have a look today.
> * ds/path-walk-1 (2024-12-07) 7 commits
> - path-walk: reorder object visits
> - path-walk: mark trees and blobs as UNINTERESTING
> - path-walk: visit tags and cached objects
> - path-walk: allow consumer to specify object types
> - t6601: add helper for testing path-walk API
> - test-lib-functions: add test_cmp_sorted
> - path-walk: introduce an object walk by path
> (this branch is used by ds/backfill.)
>
> Introduce a new API to visit objects in batches based on a common
> path, or by type.
>
> Will merge to 'next'?
> source: <pull.1818.v3.git.1733514358.gitgitgadget@gmail.com>
I was a bit late to the party, but have sent a couple of review comments
to the mailing list late last week that Derrick may want to address.
> * as/show-index-uninitialized-hash (2024-11-11) 2 commits
> - t5300: add test for 'show-index --object-format'
> - show-index: fix uninitialized hash function
>
> Regression fix for 'show-index' when run outside of a repository.
>
> Comments?
> source: <20241109092739.14276-1-abhijeet.nkt@gmail.com>
I've just had a look at it, looks good to me.
Thanks!
Patrick
next prev parent reply other threads:[~2024-12-16 8:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 12:31 What's cooking in git.git (Dec 2024, #05; Thu, 12) Junio C Hamano
2024-12-12 14:27 ` karthik nayak
2024-12-13 14:33 ` Junio C Hamano
2024-12-13 17:28 ` karthik nayak
2024-12-13 14:40 ` Christian Couder
2024-12-13 14:48 ` Junio C Hamano
2024-12-16 8:11 ` Patrick Steinhardt [this message]
2024-12-16 16:26 ` 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=Z1_gqiCuTZOdRVO0@pks.im \
--to=ps@pks.im \
--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).