So did the people at savannah.gnu.org just give up? It has been down for days.
Forge - công cụ dựa trên Git giúp giảm cập nhật thủ công cho task, tự động tổng hợp tiến độ từ commit & PR. Mục tiêu hỗ trợ thay vì thay thế phần mềm hiện tại. Dự án mở nguồn từ sinh viên CSE, mong nhận góp ý từ cộng đồng.
#Git #CôngCụLậpTrình #SourceCodeMở #QuảnLýTask #PhảnHồiLậpTrình
#DevTools #OpenSource #TaskManagement #DeveloperFeedback
#lispyGopherClimate Sunday-morning-in-Europe #peertube #live .
Short show.
https://toobnix.org/w/gXLXQqxf5MYg1NDF2Ua6oA
No gremlins (hopefully).
Just #eev #git and #slime #commonLisp #elisp useage. Then I am going to compare #ai to https://en.wikipedia.org/wiki/Blast_fishing and changes since #gof_ai .
Also! I am going to be away for the following two weeks, sorry about the unscheduled downtime.

Git 履歴をビジュアル化する新ツール「gitlogue」
https://softantenna.com/blog/gitlogue/
so I gave this to chatgpt and asked to infer meaning
it explored some guess that went too far, told to try another guess and to re-read the first line
and so it infered sequential branch merging equations
... I guess I found my new PLT denotational assistant
#llm #plt #denotation #git #gpt

@petebachant NIce, and for your #bibliography you can now do the same with #JabRef as well. We integrated pushing to #git as well in the most recent version
Looks like #github wants to require 2 factor. I was already looking for an alternative, but this seals the deal. #codeberg is great but prefers that you don't have any private repos. Alternatives?
I finally got annoyed enough with the #zerover limbo that I slapped on a v1.0.0 tag and switched to #semver for my #git utility that sets filesystem modification timestamps to the last commit that touched each file in a repository:
https://github.com/alerque/git-warp-time
No big changes, just an indication that the tool works and there is no need on the horizon to shake it up.
If you use a build system like #make that reacts to timestamps and are tired of wasted builds jump in; the water is clear of sharks.
pre-commit hooks are fundamentally broken
https://programming.dev/post/43054740
News from #sydbox #git: After ~25 commits, compilation for #Android works with bionic libc: "target/aarch64-linux-android/release/syd: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, for Android 28, built by NDK r25b (8937393), with debug_info, not stripped" Time to set up an #Android #VM and get to testing! #exherbo #linux #security
Interesting read.
I love #git. It's just so elegant and works so well, for what it's supposed to do anyway. Learning how it actually works and how to use the native #cli has yielded one of the biggest ROI, comparable only to learning #vim.
https://mastodon.social/@andrewnez/115775567916253021
🌗 為什麼 pre-commit 鉤子從根本上就是個錯誤
➤ 別讓自動化檢查成為開發效率的絆腳石
✤ https://jyn.dev/pre-commit-hooks-are-fundamentally-broken/
本文深入探討了 Git pre-commit 鉤子在實際開發流程中所導致的種種弊端。作者透過一系列 Rust 專案的實例,展示了 pre-commit 鉤子如何因為檢查「工作目錄」而非「暫存區」而失效,以及在嘗試優化後,反而於變基(rebase)或處理無關檔案時引發更多錯誤。作者認為,pre-commit 鉤子會破壞開發者將提交(commit)視為臨時存檔的習慣,嚴重幹擾本地開發節奏。最終建議開發者應捨棄 pre-commit,改用更穩定、不幹擾本地操作的 pre-push 鉤子,並堅持手動配置以確保開發環境的可控性。
+ 說得太對了!每次我只是想先 commit 把進度存下來然後去喫飯,結果 pre-commit 噴一堆格式錯誤擋住我,真的會讓人抓狂。
+ 作者提到的 `git checkout-index` 技巧確實能解決索引同步問
#Git 工作流 開發工具