Git VS vscode-gitlens

I'm confused about the timeline here, the tag for 2.50.1 is from 2025-06-16 ( https://github.com/git/git/tags ). And the date for 2.50.1 on https://git-scm.com is also 2025-06-16.

But it seems like almost no distributions have patched it yet

https://security-tracker.debian.org/tracker/CVE-2025-48386 (debian as an example)

And the security advisory is from yesterday: https://github.com/git/git/security/advisories/GHSA-4v56-3xv...

Did git backdate the release?

Clone the repository: (Replace the URL with an actual Git repository URL) git clone https://github.com/git/git.git # This will clone the Git's own source code! For a smaller example, you can use a simple hello-world repo.

They weren't, if you look at the fix [1] the dedupe loop was run in all cases, not just those with known dupes, so the performance hit was any bundle with lots of refs.

1.https://github.com/git/git/commit/bb74c0abbc31da35be52999569...

Added to Git in 2019: https://github.com/git/git/commit/209f0755934a0c9b448408f9b7...

Supported on Github in 2022: https://github.blog/changelog/2022-03-24-ignore-commits-in-t...

adoc is fine and is more widely supported. Linux (the kernel) documentation is written in adoc, along with man pages for many projects like git:

https://github.com/git/git/blob/master/Documentation/git-rm....

Git interprets a zero byte as an unconditional sign that a file is a binary file [0]. With other “nonprintable” characters (including the high-bit ones) it depends on their frequency. Other tools look for high bits, or whether it’s valid UTF-8. These rules cover different common ways to check for text vs. bonary.

[0] https://github.com/git/git/blob/683c54c999c301c2cd6f715c4114...

I second "Modern C" by Jen Gustedt.

- Get the `cdecl` tool to build intuition about function signatures. What does "int( * ( *foo)(void))[3]" mean?

- Write it yourself.

- Be disciplined. Develop good hygiene with compiler flags, memory/address checks, and even fuzzing.

- Read good source code such as the linux kernel. This is an amusing header file from the linux kernel that defines some banned files. This is wisdom if you choose to follow it: https://github.com/git/git/blob/master/banned.h

- Push the language to its limits. Play with memory and data structures. Inspect everything. This book "Data-Oriented Design" by Richard Fabien is a great to explore as well. It's about organizing your data for efficient processing.

Well it's free software and open source, right? https://github.com/gitkraken/vscode-gitlens/blob/main/LICENS...

Eventually someone will fork it just to remove the ads

Github: Gitlens Marketplace: Gitlens

IntelliJ: https://www.jetbrains.com/help/idea/investigate-changes.html

VSCode:

https://marketplace.visualstudio.com/items?itemName=mhutchie...

or https://github.com/gitkraken/vscode-gitlens#commit-graph-

SourceTree: https://confluence.atlassian.com/sourcetreekb/viewing-log-hi...

Quite a while ago, the GitLens+ plugin gained the Commit Graph feature--the same graph you see in GitKraken. Until then I had used Git Graph for visualizing my repositories and GitLens+ for git blame in the GUI. Since one plugin could now do both, the natural course of action was to remove the other--goodbye, Git Graph!

Btw, today I want to speak about something different, I love git and I love terminal, but sometimes I love having the info visualised appealingly and get info about the source control quickly. I work with VsCode typically, so some months ago I tried to find a solution for this editor that resolves what was said before. After googling and some testing, the result of my search was: GitLens. Now, I want to show you how it works and how it can improve your routine. So don't waste time and let's jump in it!

GitLens extension chef's kiss

for GitLens https://gitlens.amod.io/

The better version is to have something like gitlens installed into your IDE and have it dynamically render those git comments.

https://github.com/Axosoft/vscode-gitlens#current-line-blame...