The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Email Subscription

    Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 717 other subscribers

Archive for the ‘git’ Category

Git files hidden in plain sight 🫥 – Tyler Cipriani

Posted by jpluimers on 2026/11/05

Infinite magic awaits the intrepid developer willing to abuse git plumbing. After all, git is just a database with a terrible interface.

From [Wayback/Archive] Git files hidden in plain sight 🫥 – Tyler Cipriani

I wonder how various endpoint security solutions handle this (:

Via:

–jeroen

Posted in Blue team, Development, DVCS - Distributed Version Control, git, GitHub, Power User, Red team, Security, Software Development, Source Code Management | Leave a Comment »

ipmitool/sf2gh: migrates tickets to GH from SF

Posted by jpluimers on 2026/09/29

Just in case I ever want to migrate a repository from SourceForge to GitHub: [Wayback/Archive] ipmitool/sf2gh: migrates tickets to GH from SF

This was developed for the Gene Ontology but is generic and will work for any project.

The project consists of two files, the extensive [Wayback/Archive] sf2gh/README.md at master · ipmitool/sf2gh · GitHub which has a very important tip:

Read the rest of this entry »

Posted in cURL, Development, DVCS - Distributed Version Control, git, GitHub, JavaScript/ECMAScript, Perl, Software Development, Source Code Management, SourceForge | Leave a Comment »

The Git Commands I Run Before Reading Any Code

Posted by jpluimers on 2026/09/22

When joining or assessing a team or taking up a codebase, be sure to run these five git commands to get a quick overview on the state of affairs: [Wayback/Archive] The Git Commands I Run Before Reading Any Code

These five commands take a couple minutes to run. They won’t tell you everything. But you’ll know which code to read first, and what to look for when you get there. That’s the difference between spending your first day reading the codebase methodically and spending it wandering.

This is the first hour of what I do in a codebase audit. Here’s what the rest of the week looks like.

Via [Wayback/Archive] Jocelynephiliac :reclaimer:: “This all really good, love thi…” – Twipped Social (Private):

This all really good, love this. It’s all analyzing social behaviors, not code at all.

“Five git commands that tell you where a codebase hurts before you open a single file. Churn hotspots, bus factor, bug clusters, and crisis patterns.”

The commands:

Read the rest of this entry »

Posted in Development, DVCS - Distributed Version Control, git, Software Development, Source Code Management | Leave a Comment »

GitHub – omegat-org/git-svn-sync: Continuously sync a svn to git, in the cloud.

Posted by jpluimers on 2026/06/18

Interesting: [Wayback/Archive] GitHub – omegat-org/git-svn-sync: Continuously sync a svn to git, in the cloud.

It lives in the Amazon cloud, but should be adaptable to other cloud providers.

Query: [Wayback/Archive] service to sync between sourceforge svn and github git at DuckDuckGo

--jeroen

Posted in Development, DVCS - Distributed Version Control, git, GitHub, Software Development, Source Code Management, Subversion/SVN | Leave a Comment »

Don’t forget you also have a personal gitignore file in $HOME/.config/git/ignore

Posted by jpluimers on 2026/05/28

The question in [Wayback/Archive] git – What will happen when a pull request includes changes to ignored .gitignore? – Super User comes down to:

I don’t want anybody to change what’s in my .gitignore file because it includes some things that are specific to my own system.

Those settings should go in a personal gitignore file, which is mentioned in the [Wayback/Archive] Git – gitignore Documentation

Read the rest of this entry »

Posted in Development, DVCS - Distributed Version Control, git, Software Development, Source Code Management, Versioning | Leave a Comment »

A lot of GitLab pages links and Git pushing a relatively large commit to GitLab: “error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502”

Posted by jpluimers on 2026/05/27

Got an error when pushing a relatively large commit to GitLab: error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502

There was no big difference in information between these commands¹:

  1. git push
  2. git push --verbose

Read the rest of this entry »

Posted in //e, 6502, Apple, Apple ///, Apple IIgs, Apple ][, Development, DVCS - Distributed Version Control, git, GitLab, History, Power User, Software Development, Source Code Management, Versioning | Leave a Comment »

Beeper — All your chats in one app

Posted by jpluimers on 2026/05/13

[Wayback/Archive] Beeper — All your chats in one app

Via a friend that mentioned Beeper to me.

On the list to try out somewhere during the year.

It is open source; some more links:

Read the rest of this entry »

Posted in Chat, Development, Discord, DVCS - Distributed Version Control, Facebook, git, GoogleChat, IRC, LinkedIn, Power User, Signal messenger, SocialMedia, Software Development, Source Code Management, Telegram, Twitter, WhatsApp | Leave a Comment »

Arjen Lentz Crystal Ball Vulnerability Prediction: A Wizard’s Guide to Foreseeing the Unseen: NLUUG voorjaarsconferentie, 7 mei 2026, Arjen Lentz over de echte root cause van veel CVE’s en hoe die te fixen

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 »

Dare Obasanjo: “GitHub … How many other services are painting a far rosier picture than reality on their service status pages?” – mas.to

Posted by jpluimers on 2026/04/30

Last 90 days uptime on 20260427 of the GitHub Platform, 87.25% uptime, by Marek Šuppa @mareksuppa

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 »

Importing a repository with GitHub Importer – GitHub Docs

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 »