Archive for the ‘git’ Category
Posted by jpluimers on 2025/06/24
A few years back, a few interesting files turned up that are directly served from the testla.com web-site right in the middle when Musk used their software engineers to asses twitter.com code quality:
Some do not exist (of which some any more):
Read the rest of this entry »
Posted in Development, DVCS - Distributed Version Control, git, PHP, Scripting, Software Development, Source Code Management, Web Development | Tagged: 3088938 | Leave a Comment »
Posted by jpluimers on 2025/04/15
Empirically, these are show the same behaviour where “command 2″and “command 3″are documented, but still present a lot as the only solution in blog posts and help sites:
git config commands
command 1: list |
command 2: --list |
command 3: -l |
what config is shown |
git config list --local |
git config --list --local |
git config -l --local |
--local config for current repository |
git config list --global |
git config --list --global |
git config -l --global |
--global config for the current user |
git config list --system |
git config --list --system |
git config -l --system |
--system config for all users |
git config list |
git config --list |
git config -l |
all 3 levels of config combined, for convenience
without telling which configuration setting is on which level |
Based on [Wayback/Archive] git config: list all variables and their default values – Stack Overflow (thanks [Wayback/Archive] Matteo Meil): Read the rest of this entry »
Posted in Development, DVCS - Distributed Version Control, git, Software Development, Source Code Management, Versioning | Leave a Comment »
Posted by jpluimers on 2025/03/31
A few years back I had an error happen a while on one of my Windows machines after a git pull: fatal: detected dubious ownership in repository at 'C:/versioned/repository' followed by a few lines with Windows SIDs (Security Identifiers) that I had to map to actual users.
I thought I had it scheduled, but my notes were in a draft post, so when I bumped into it again when upgrading an old virtual machine with new versions I finished it and scheduled it for now.
The first time I got the error was after git for Windows fixed security vulnerability [Wayback/Archive] CVE-2022-24765 and included the quote from [Wayback/Archive] Uncontrolled search for the Git directory in Git for Windows · Advisory · git-for-windows/git:
Read the rest of this entry »
Posted in CommandLine, Development, DVCS - Distributed Version Control, git, Power User, PowerShell, PowerShell, Scripting, Software Development, Source Code Management, Windows, Windows 10, Windows 11, Windows 7 | Tagged: 11 | Leave a Comment »
Posted by jpluimers on 2025/03/20
Since git doesn’t have the notion of directories as entities, neither does GitHub.
This makes it counter-intuitive to add a sub-directory when creating a new file on-line in the GitHub web-UI or uploading file(s) there.
I wanted to do this as instead of taking the local route, it was easier to on-line add and edit [Wayback/Archive] GitHub – jpluimers/https-imgur.com-a-bmw-e61-remote-fix-sWdk0: Content from https://imgur.com/a/bmw-e61-remote-fix-sWdk0 for Wayback Machine archival.
The GitHub web-UI can indeed do this:
Further reading
You can also do this from the git command-line, by adding an empty file in the directory first. By convention, usually a .gitkeep file is used for that though others use .gitignore files for it.
Read the rest of this entry »
Posted in Development, DVCS - Distributed Version Control, git, GitHub, Software Development, Source Code Management | Tagged: 21962 | Leave a Comment »
Posted by jpluimers on 2024/11/12
[Wayback/Archive] GitHub – src-d/hercules: Gaining advanced insights from Git repository history.
This project, with the command-line tools hercules and labours is on my research list as it can get pretty good long-term insights on project health (the tool is programming language independent).
Especially the half-life of code is a good measurement, as well as the existence of code bursts (hello major version increments!).
This research part is important: [Wayback/Archive] Change Bursts as Defect Predictors – Publications – Software Engineering Chair (Prof. Zeller), by Nachiappan Nagappan, Andreas Zeller, Thomas Zimmermann, Kim Herzig, Brendan Murphy
Read the rest of this entry »
Posted in BASTA!, Conference Topics, Conferences, Development, DVCS - Distributed Version Control, EKON, git, ITDevCon, Software Development, Source Code Management, Static Code Analysis | Leave a Comment »
Posted by jpluimers on 2024/11/07
This one is clear and concise. [Wayback/Archive] liburing/CONTRIBUTING.md at master · axboe/liburing · GitHub of which some highlights:
…
The main reasons for the rules are:
- Keep the code consistent
- Keep the git repository consistent
- Maintain bisectability
…
No fixup commits! Sometimes people post a change and errors are pointed out in the commit, and the author then does a followup fix for that error. This isn’t acceptable, please squash fixup commits into the commit that introduced the problem in the first place. This is done by amending the fix into the original commit that caused the issue. You can do that with git rebase -i and arrange the commit order such that the fixup is right after the original commit, and then use ‘s‘ (for squash) to squash the fixup into the original commit. Don’t forget to edit the commit message while doing that, as git will combine the two commit messages into one. Or you can do it manually. Once done, force push your rewritten git history. See reasons 1-3 in the introduction series for why that is.
…
A good commit explains the WHY of a commit – explain the reason for this commit to exist. Don’t explain what the code in commit does, that should be readily apparent from just reading the code. liburing commits follow the following format:
Read the rest of this entry »
Posted in Development, DVCS - Distributed Version Control, git, Open Source, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2024/10/24
Posted in Conference Topics, Conferences, Development, DVCS - Distributed Version Control, Event, git, Google, GoogleSearch, Pingback, Software Development, Source Code Management, Stackoverflow | Leave a Comment »
Posted by jpluimers on 2024/09/26
A while ago [Wayback/Archive] b0rk (Julia Evans [Wayback/Archive) wrote an interesting Tweet on finding back where you broke code of which the OCR text reads like this:
strategy: change working code into broken code
If I have a working version of the program, I like to:
- go back to the working code
- slowly start changing it to be more like my broken code
- test if it’s still working after every single tiny change
· ⬊⸳⬈˙⬊⸳⬈˙⬊⸳ OH THAT’S WHAT BROKE IT!!!
I like this because it puts me back on solid ground: with every change make that DOESN’T cause the bug to come back, I know that wasn’t the problem.
by JULIA EVANS @bork wizardzines.com
This is similar (her arrows were of varying length) to using a binary search algorithm hunting for where the code was broken using bisection: repeatedly halving your search space to quickly zoom into the problem.
Another important aspect is that small commits while fiddling to solve an issue can help you determine what small commit was actually solving the issue.
Read the rest of this entry »
Posted in Algorithms, Conference Topics, Conferences, Development, DVCS - Distributed Version Control, Event, git, Mercurial/Hg, Ruby, Software Development, Source Code Management, Versioning | Leave a Comment »
The Wiert Corner - irregular stream of stuff 