GripNews (@GripNews@mastodon.social)
🌘 我的新 Git 工具 `what-changed-twice` 需要一個新名字
➤ 用新工具優化 Git 提交歷史整理流程
✤ https://blog.plover.com/2025/09/21/#what-changed-twice
作者 Mark Dominus 分享了他為 Git 工作流程開發的新工具 `what-changed-twice`（暫定名為 Fred）。這個工具旨在協助開發者整理提交（commit）歷史，特別是在同一個檔案被多次修改時。它能分析 `git log` 的輸出，找出在多個提交中被修改過的檔案，並報告哪些檔案在哪些提交中出現變動，藉此幫助使用者識別哪些變動可能需要合併（squash）或重組，以產出更清晰的提交歷史。作者坦承自己不擅長命名，並徵求新名稱建議。
+ 這個工具聽起來很有用！我常常也需要花很多時間整理 Git 提交，特別是處理錯字修改和階段性 WIP 提交。期待看到這個工具的正式名稱和更多介紹。
+ 作者的思路很有趣，將 Git 的混亂提交整理成有意義的歷史。不過，如果能直接整合進 Git 命令，而不是另外
#程式設計 #Git #工作流程
Show Original Post
hackernews_bot_vn (@hackernews_bot_vn@mastodon.maobui.com)
Tác giả đang tìm tên mới cho công cụ Git `what-changed-twice` của mình. Công cụ này giúp theo dõi những thay đổi trong mã nguồn một cách hiệu quả. Ai có đề xuất hay không? 🛠️💡
#Git #CôngCụPhátTriển #LậpTrình #OpenSource #DeveloperTools
https://blog.plover.com/2025/09/21/#what-changed-twice
Show Original Post
osunderdog (@osunderdog@dmv.community)
My afternoon was spent migrating my personal code projects from Google Source Code Repositories to self-hosted.
I have ~45 repos with personal code fiddling that I don't want to lose. Or perhaps I'm just hoarding data that I will never look at again.
I moved to a on-prem server using git remote ssh specification. Now I just need to remember to build some backup policy for the on-prem server.
Show Original Post
goku12 (@goku12@fosstodon.org)
Hey guys! If you're planning to learn #rustlang, don't choose to rewrite any big classic software suite like the GNU #coreutils or #git as your first project. For all your noble intentions, someone will pick it up to replace the classic counterpart with, in some popular Linux distro. Then they'll stumble upon the innocent mistakes you made due to your inexperience. Someone else will make a magazine article out of it and everyone will crucify you and Rust publicly for it.
Show Original Post
kramse (@kramse@helvede.net)
Nice, while reading about git in the Missing Semester course from MIT at
https://missing.csail.mit.edu/2020/version-control/
They do a bottom-up explanation of Git, that actually helps me a lot.
Also recommend and link to:
https://git-scm.com/book/en/v2
The entire Pro Git book, written by Scott Chacon and Ben Straub and published by Apress, is available here. Links to PDF and ePUB!
I might have been down this road before, but the links can be repeated :-D
Show Original Post
ethauvin (@ethauvin@mastodon.social)
Git Developers Debate Making Rust Mandatory
https://www.phoronix.com/news/Git-Weighs-Mandatory-Rust
Show Original Post
kpcyrd (@kpcyrd@chaos.social)
@gbraad It most likely would have.
CVE-2025-48385 is almost guaranteed, as long as the `url` crate would've been used, which rejects this as invalid.
CVE-2025-48386 is explicitly a memory safety problem.
CVE-2025-48384 is hard to say, gitoxide did implement this correctly, testing both the first and last character for u8::is_ascii_whitespace.
#git #rust
Show Original Post
snacktraces (@snacktraces@hachyderm.io)
Hey software development newbies
I will be offering this again this week. This might be my last opportunity to do for a while as I foresee changes coming for me.
Need a pairing buddy to help learn about/more about git? Git, a popular/commonly used source control tool for software development, can be a bit tricky to learn.
Maybe even some intro to programming? Maybe us pairing on a little project?
I would like to offer some live pairing if anyone is interested.
Free of charge, just wanting to share with someone who could use it. DM me if interested.
#SoftwareDevelopment. #git. #newbies
Show Original Post
snacktraces (@snacktraces@hachyderm.io)
Hey software development newbies
I will be offering this again this week. This might be my last opportunity to do for a while as I foresee changes coming for me.
Need a pairing buddy to help learn about/more about git? Git, a popular/commonly used source control tool for software development, can be a bit tricky to learn.
Maybe even some intro to programming? Maybe us pairing on a little project?
I would like to offer some live pairing if anyone is interested.
Free of charge, just wanting to share with someone who could use it. DM me if interested.
#SoftwareDevelopment. #git. #newbies
Show Original Post
hackernews_bot_vn (@hackernews_bot_vn@mastodon.maobui.com)
Khám phá cách trực quan hóa 12 lệnh Git trong không gian 3D! 🚀 Video này mang đến góc nhìn không gian độc đáo về kiểm soát phiên bản, giúp hiểu sâu hơn các thao tác Git qua hình ảnh động sinh động. #Git #VersionControl #LậpTrình #KiểmSoátPhiênBản #CôngNghệ
https://www.youtube.com/watch?v=C2aFC8wFp2A
Show Original Post
exfalsoquodlibet (@exfalsoquodlibet@piaille.fr)
One manpage a day keep the boredom away.
Options for `git blame` command:
1. `--first-parent` allows to get the merge commit (if any) that introduce / change a line
2. `-L` allows to limit the annotations to a range of line
Hence:
```sh
$ git blame --first-parent -L LINE,+1 FILENAME | cut -d ' ' -f 1 | xargs git show
```
will show the merge commit last modifying LINE in FILENAME.
Very useful when the cover letter of a patchset is incuded in the merge commit message (which I believe should be good practice).
Show Original Post
