Top all-time · #3111
[bobulate]
Personal blog · euroquis.nlprogrammingsystems
[bobulate] is a personal blog at euroquis.nl about programming and systems. Since 2011, 24 different Hacker News readers have linked it 42 times, most often “Git Alligator”. It is still writing: the last post was on 2026-02-02, and you can follow it by feed.
My personal site of programming, C++, baking, KDE and FreeBSD things.
Most-linked posts?
- Git Alligator3 people · 4 mentions · first linked 2020-08-09
- File Modes in C++202 people · 2 mentions · first linked 2024-05-01
- Strong Booleans2 people · 2 mentions · first linked 2022-11-21
- Python and SysV Shared Memory2 people · 2 mentions · first linked 2024-10-09
- Needlessly Public2 people · 2 mentions · first linked 2024-06-07
What Hacker News says?
I think the scenario you've described assumes that the branches have diverged -- that each branch has a commit not on the other. But if you always rebase your branch onto `develop` before merging, your branch definitively has no conflicts. If you then use `--no-ff` to merge, it will create a merge commit anyway. This article shows what I mean: https://euroquis.nl/blabla/2019/08/09/git-alligator.html . (The only thin…
Comment linking /blabla/2019/08/09/git-alligator.html
on “Things I wish Git had: Commit groups”Submitted Framework 13 AMD Setup with FreeBSD as a story · 65 points
HN discussionFor the best of both worlds, I like the "git alligator" workflow: always perform a merge commit when adding a feature, then use `git log --first-parent` to browse the history without seeing the intermediate commits. https://euroquis.nl/blabla/2019/08/09/git-alligator.html first parent log isn't mentioned, though.
Comment linking /blabla/2019/08/09/git-alligator.html
on “Fortunately, I don't squash my commits”Submitted Python and SysV Shared Memory as a story · 63 points
HN discussionI still wish people would give meaningful names to their merge commits. Together with `git log --first-parent` and the alligator [1] workflow, it can filter out the less interesting patch series to focus on the bigger picture (the fact that you added a functionality, not that it took you 53 commits changing very specific parts to do so). [1]: https://euroquis.nl/blabla/2019/08/09/git-alligator.html
Comment linking /blabla/2019/08/09/git-alligator.html
on “Linux 5.8-rc1”Submitted KDE FreeBSD 2020.1 as a story · 28 points
HN discussionKDE 5 is in progress, you can already try it http://euroquis.nl/bobulate/?p=1609 Closing the lid is a non-issue, see sysctl hw.acpi.lid_switch_state. A more serious problem is that some Thinkpads just don't wake up https://github.com/FreeBSDDesktop/freebsd-base-graphics/issu... :( This was already mentioned here but what's up with people thinking that ZFS is only for large storage arrays? You don't need anything mor…
Comment linking /bobulate/?p=1609
on “FreeBSD 11.1 released”Submitted Where in the Stack? as a story · 18 points
HN discussionI also encourage everybody I know to write descriptive merge commits: "Merge feature X" instead of "Merge someone/master into master". It really helps when using git log --first-parent to avoid displaying intermediate messages. This really helps with the so-called "Aligator" [1] workflow: create a merge commit for every bugfix or feature, instead of just rebasing (you can still rebase if you want). That makes the hi…
Comment linking //bla%20bla/2019/08/09/git-alligator.html
on “Rob Pike on good commit messages (2014)”Submitted Needlessly Public as a story · 8 points
HN discussionFreeBSD wiki is a bit notorious for being out-of-date, and that particular page is marked “CategoryStale”. Anyway, first result on DuckDuckGo is someone using Wayland on FreeBSD successfully [1]. [1]: https://euroquis.nl/freebsd/2021/03/16/wayland.html
Comment linking /freebsd/2021/03/16/wayland.html
on “Xorg-Server 21.1.0”Submitted KDE Plasma 6 Wayland on FreeBSD as a story · 7 points
HN discussionIf anyone's interested, there's a slightly more recent update on this work at the link below, dated about a week after this post (23 March vs. 16 March 2025 on the main link). [1] https://euroquis.nl/freebsd/2025/03/23/framework.html
Comment linking /freebsd/2025/03/23/framework.html
on “Framework 13 AMD Setup with FreeBSD”Submitted FreeBSD on Slimbook – 14 months of updates as a story · 4 points
HN discussionSubmitted Python and SysV Shared Memory as a story · 3 points
HN discussionSubmitted Calamares ABI Checking as a story · 3 points
HN discussionSubmitted That is how E-Waste is made as a story · 2 points
HN discussionSubmitted File Modes in C++20 as a story · 2 points
HN discussionSubmitted FreeBSD and KDE's Megarelease 6 as a story · 2 points
HN discussionSubmitted C++ Guidelines as a story · 2 points
HN discussionSubmitted C++23 Characters as a story · 2 points
HN discussionSubmitted Memory Disks as a story · 2 points
HN discussionSubmitted Steam on FreeBSD (2021) as a story · 2 points
HN discussionSubmitted Strong Booleans as a story · 2 points
HN discussionSubmitted 80/20 Refactoring as a story · 2 points
HN discussionSubmitted How Not to Execve() as a story · 2 points
HN discussionSubmitted Wayland on FreeBSD as a story · 2 points
HN discussionSubmitted Akonadi / KMail and Google accounts resolved as a story · 2 points
HN discussionSubmitted FreeBSD Progress on Slimbook Base14 as a story · 2 points
HN discussionSubmitted KDE FreeBSD updates (february 2020) as a story · 2 points
HN discussion
