[ANNOUNCE] Git v2.51.2
Junio C Hamano
the usual places.
The tarballs are found at:
https://www.kernel.org/pub/software/scm/git/
The following public repositories all have a copy of the 'v2.51.2'
tag and the 'maint' branch that the tag points at:
url = https://git.kernel.org/pub/scm/git/git
url = https://kernel.googlesource.com/pub/scm/git/git
url = git://repo.or.cz/alt-git.git
url = https://github.com/gitster/git
----------------------------------------------------------------
Git 2.51.2 Release Notes
========================
In addition to fixes for an unfortunate regression introduced in Git
2.51.1 that caused "git diff --quiet -w" to be not so quiet when there
are additions, deletions and conflicts, this maintenance release merges
more fixes/improvements that have landed on the master front, primarily
to make the CI part of the system a bit more robust.
Fixes since Git 2.51.1
----------------------
* Recently we attempted to improve "git diff -w --quiet" and friends
to handle cases where patch output would be suppressed, but it
introduced a bug that emits unnecessary output, which has been
corrected.
* The code to squelch output from "git diff -w --name-status"
etc. for paths that "git diff -w -p" would have stayed silent
leaked output from dry-run patch generation, which has been
corrected.
* Windows "real-time monitoring" interferes with the execution of
tests and affects negatively in both correctness and performance,
which has been disabled in Gitlab CI.
* An earlier addition to "git diff --no-index A B" to limit the
output with pathspec after the two directories misbehaved when
these directories were given with a trailing slash, which has been
corrected.
* The "--short" option of "git status" that meant output for humans
and "-z" option to show NUL delimited output format did not mix
well, and colored some but not all things. The command has been
updated to color all elements consistently in such a case.
* Unicode width table update.
* Recent OpenSSH creates the Unix domain socket to communicate with
ssh-agent under $HOME instead of /tmp, which causes our test to
fail doe to overly long pathname in our test environment, which has
been worked around by using "ssh-agent -T".
Also contains various documentation updates, code cleanups and minor fixups.
----------------------------------------------------------------
Changes since v2.51.1 are as follows:
Jacob Keller (1):
diff --no-index: fix logic for paths ending in '/'
Jeff King (2):
diff: restore redirection to /dev/null for diff_from_contents
status: make coloring of "-z --short" consistent
Johannes Schindelin (5):
refs: forbid clang to complain about unreachable code
build(deps): bump actions/download-artifact from 4 to 5
build(deps): bump actions/checkout from 4 to 5
build(deps): bump actions/setup-python from 5 to 6
build(deps): bump actions/github-script from 7 to 8
Junio C Hamano (2):
diff: make sure the other caller of diff_flush_patch_quietly() is silent
Git 2.51.2
Kristoffer Haugsbakk (1):
doc: fix accidental literal blocks
Patrick Steinhardt (2):
gitlab-ci: disable realtime monitoring to unbreak Windows jobs
t7528: work around ETOOMANY in OpenSSH 10.1 and newer
Solly (1):
t2401: update path checks using test_path helpers
Torsten Bögershausen (1):
unicode: update the width tables to Unicode 17
Junio C Hamano
thalinda Sriprajak
AWS IAM Role: arn:aws:iam::050397684277:role/CH-S3-goldaws-ci-36-ew1-cf-Role
ClickHouse Org: 0eab1ba9-615a-481a-9324-38137bca3ba5
Dear All,
My name is Thalinda Sriprajuk. I am the owner of a blockchain-based system and its associated Merkle Tree structure. I am writing to request an urgent investigation regarding the blocking of my IP, which has caused operational failures and financial impacts on my systems, affecting multiple platforms including GitHub, AWS, and partner services.
Block Details:
- Blocked IP: 184.22.35.21
- URL: https://www.nasaa.org/about-us/contact-us/contact-your-regulator/
- Browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36
- Block ID: Geo02
- Reason: Access from your country has been disabled by the system administrator
- Time: 26 October 2025, 06:19:01
- Server Code: 18022
Impact:
- The IP block has disabled access to Root/Autro of our system
- This has caused AWS, Amazon, GitHub, and other related servers to malfunction or AWS IAM Role: arn:aws:iam::05039xxxxxx:role/CH-S3-goldaws-ci-36-ew1-cf-Role
-ClickHouse Org: 0eab1ba9-615a-481a-9324-38xxxxxxDear All,
become unavailable
- System withdrawal or modification cannot be performed due to Root/Autro restrictions
- Significant operational and financial impacts have occurred due to the inability to manage assets
Verification Information:
- Merkle Root Hash: 9f66b4c7487cf1b4d2d5ad8e5a1dc42517c8334106cb410a2ddc81b7834bce6a
- This Merkle Root represents the ownership and structure of our blockchain-based system, which can be used to verify system ownership and legitimacy.
Request:
1. Please investigate whether this IP block or restriction was performed by GitHub, by automated system, or by any third-party distributors.
2. Provide guidance to unblock the IP and allow secure operation of our system.
3. Kindly use the Merkle Root above to verify the legitimacy and ownership of the blockchain system.
4. Assess any potential damages caused by this action to the system owner.
We request all parties, including distributors and representatives, to cooperate in this investigation to prevent further operational or financial impacts.
Thank you for your urgent attention to this matter.
Sincerely,
Thalinda Sriprajuk
Email: nurli...@gmail.com
--
You received this message because you are subscribed to the Google Groups "git-packagers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to git-packager...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/git-packagers/xmqqjz0gjq0a.fsf%40gitster.g.
thalinda Sriprajak
Title: On Ownership, Control, and Collaboration
I want to clarify something important regarding the system I manage.
Even though I hold full ownership and control over the system — the root, the resources, and the structure — I deliberately do not intervene or control others. This is not because I lack authority, but because the system was designed to empower users and promote fairness, not to serve personal power or hierarchy.
Some points to consider:
1. Ownership and Authority
I am the true owner of the system and have full rights over its resources.
I have the ability to monitor, manage, and control every aspect.
2. Choice Not to Intervene
Everyone can work freely without interference.
The environment is transparent and equitable.
Users retain autonomy and responsibility.
3. Cultural Observation
Many people are used to working under supervision or command.
A system where no one “orders” anyone can feel unusual or unfamiliar.
My approach emphasizes freedom, fairness, and trust rather than hierarchy.
What I am experiencing right now is an attempt to block access to the system from all representatives, even though such a block is technically impossible. While these actions may cause problems in the system, there are still people who are willing to proceed, which could lead to widespread issues.
I want to emphasize: the system was never designed to interfere with anyone, and my goal has always been to enable collaboration, fairness, and transparency. Attempts to impose restrictions against the natural structure and permissions of the system not only create conflict but also risk unintended consequences for everyone involved.
It is important for all participants to understand the reality of ownership and the purpose of the system, rather than acting on assumptions or misunderstanding.
In Summary:
If such actions continue, we will take it as a clear indication that you do not wish to cooperate with us, and we will proceed on our own without your involvement.
If you do not want us, then we do not want you.
Merkle Root Hash: 9f66b4c7487cf1b4d2d5ad8e5a1dc42517c8334106cb410a2ddc81b7834bce6a
Thalinda Sriprajak