Archive for the ‘Source Code Management’ Category
Posted by jpluimers on 2026/05/04
Ook vandaag even een herinnering aan de NLUUG voorjaarsconferentie 2026 van (komende) donderdag 7 2026 mei in het Van der Valk Hotel Utrecht¹.
Deze keer omdat een goede vriend van me daar spreekt. Arjen Lentz heeft het over A Wizard’s Guide to Foreseeing the Unseen.
Dat klinkt misschien vaag, het concrete resultaat is dat je met analyse van CVE’s veel te weten komt over hun echte root cause. Die blijkt verrassend voorspelbaar, is fixbaar, en kennis daarover is niet alleen nuttig voor adversaries. Het kan jou namelijk helpen bij de development en selectie van wat je zelf gebruikt.
Het volledige programma staat hieronder², eerst de aankondiging van [Wayback/Archive] L⭕️rd Quux RCX CCX: “Over een week is het zover! De enige NLUUG conferentie van 2026. …” – Mastodon
Read the rest of this entry »
Posted in Blue team, Development, DVCS - Distributed Version Control, git, Infosec (Information Security), Power User, Red team, Security, Software Development, Source Code Management, Systems Architecture | 1 Comment »
Posted by jpluimers on 2026/04/30
Last 90 days uptime on 20260427 of the GitHub Platform: 87.25%
Because of two alternative GitHub status pages, a lot of people now realise that GitHub gives a rosier result than the official pages.
April uptime not even had one nine, dropping below 89%.
Which begs this interesting question
“How many other services are painting a far rosier picture than reality on their service status pages?” by Dare Obasanjo: “GitHub just published a blogpo…” – mas.to:
Read the rest of this entry »
Posted in Development, DVCS - Distributed Version Control, git, GitHub, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2026/04/20
Via [Wayback/Archive] Importing a repository with GitHub Importer – GitHub Docs I found [Wayback/Archive] Import repository · GitHub which can import from Subversion, Mercurial, TFVC, and Git as per [Wayback/Archive] About GitHub Importer – GitHub Docs.
Note this will import the repository, but not any surrounding things (like tickets/issues, wiki, etc).
In that sense, the more than 10 year old [Wayback/Archive] SourceForge: GitHub Project Importer as documented in [Wayback/Archive] SourceForge Support / Documentation / GitHub Importer does a way better job the other way around.
If you want to import more than just a repository into GitHub, then some inspiration is at [Wayback/Archive] Migrate from Sourceforge to Github – Stack Overflow (thanks [Wayback/Archive] Matthew Talbert, [Wayback/Archive] Masood Khaari, [Wayback/Archive] Thomas and [Wayback/Archive] Sergey Ponomarev) for instance with these tools:
Especially the last one is interesting as it allows you to separate tickets from repository import. This opens up the opportunity to do the svn to git conversion yourself and keep that conversion in place to you can use it to sync incoming svn changes towards the git repository.
The above does not cover CVS. For that, be sure to read these:
Via [Wayback/Archive] import sourceforge into github – Google Search.
–jeroen
Posted in Development, DVCS - Distributed Version Control, git, GitHub, Software Development, Source Code Management, SourceForge, Subversion/SVN | Leave a Comment »
Posted by jpluimers on 2026/03/24
You can find the binary files sound files of the Mastodon beep sound at
They were created by [Wayback/Archive] Josef Kenny (blog: [Wayback/Archive] josef.one; Mastodon “i made that mastodon boop sound”: [Wayback/Archive] josef (@jk@mastodon.social) – Mastodon) early 2017 and updated with metadata later that year. In 2022 it became clear that using the sound is allowed as long as there is credit:
Read the rest of this entry »
Posted in Audio, Development, DVCS - Distributed Version Control, git, GitHub, Mastodon, Media, Power User, SocialMedia, Software Development, Source Code Management | Tagged: 25827, 5531 | Leave a Comment »
Posted by jpluimers on 2026/03/17
During a Cloudflare outage¹, I learned about [Wayback/Archive] Wisp.place Documentation | Wisp.place Docs
Decentralized static site hosting on the AT Protocol.
Wisp.place enables you to host static websites directly in your AT Protocol repository. Your Personal Data Server (PDS) holds the cryptographically signed manifest and files as the authoritative source of truth, while hosting services index and serve them with CDN-like performance.
This is the documentation of [Wayback/A] wisp.place by [Wayback/Archive] Ana (@nekomimi.pet) — Bluesky.
Related:
Read the rest of this entry »
Posted in CDN (Content Delivery Network), Cloud, Cloudflare, Development, DVCS - Distributed Version Control, git, Hosting, Infrastructure, Power User, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2025/12/25
Posted in Conference Topics, Conferences, Development, DVCS - Distributed Version Control, Event, git, GitHub, Hardware, Network-and-equipment, pfSense, Power User, routers, Software Development, Source Code Management, Tailscale | Tagged: 11281, 73 | Leave a Comment »
Posted by jpluimers on 2025/12/16
[Wayback/Archive] version control – How can I see the changes in a Git commit? – Stack Overflow (thanks [Wayback/Archive] laktak, [Wayback/Archive] Nevik Rehnel, [Wayback/Archive] Juuso Ohtonen and [Wayback/Archive] User c z – Stack Overflow)
This looks like a valid question, but in reality it is not.
The thing is: in git, think of a commit not as a diff but as a snapshot*.
A diff is the difference between two commits.
Since most commits have just a single parent, so that’s why many people call a commit a diff. But that’s not true, especially not for merge commits that have at least two parents.
Anyway, the question, answer and comment from the link above already give some insight (note COMMIT everywhere below has to be replaced with the commit hash):
Read the rest of this entry »
Posted in Conference Topics, Conferences, Development, DVCS - Distributed Version Control, Event, git, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2025/12/04
I used [Wayback/Archive] How could i get a permanent link for raw file? · community · Discussion #22537 · GitHub to go
The reason I needed it is that for quite a while now, GitHub has started to display PDF files as preview, and modified the download behaviour to get a blob: link instead of the actual raw file download location.
On the to do list:
- figure out the same for raw files in gists
- figure out the same for GitLab
- convert these into Bookmarklets (fiddle with the bold parts in the above URLs)
Thanks [Wayback/Archive] Lotaristo (Czeslaw Meyer) and [Wayback/Archive] byrneh (Hugh Byrne)
--jeroen
Posted in Bookmarklet, Conference Topics, Conferences, Development, DVCS - Distributed Version Control, Event, gist, git, GitHub, GitLab, Hosting, JavaScript/ECMAScript, Power User, Scripting, Software Development, Source Code Management | Tagged: 22537 | Leave a Comment »
The Wiert Corner - irregular stream of stuff 