Posted by jpluimers on 2018/04/11
[WayBack] Gource – software version control visualization has example for these kinds of repositories: Git, Bazaar, Mercurial and SVN.
Source: acaudwell/Gource: software version control visualization
Cool tool (works on Windows and Linux) that I found via [WayBack] Juancarlo Añez – Google+
–jeroen
Posted in Development, DVCS - Distributed Version Control, git, Mercurial/Hg, Software Development, Source Code Management, Subversion/SVN | Leave a Comment »
Posted by jpluimers on 2018/04/08
OSC downloads for [archive.is] https://bugzilla.opensuse.org/show_bug.cgi?id=1084812
The binaries provided by Stefan Brüns, together with installation instructions are now in a git repository at [WayBack] wiert.me/public/linux/opensuse/tumbleweed/aarch64 a.k.a. arm64/1084182-fix-osc-binaries · GitLab.
Follow the steps in Applying the fixes on a broken system to at least temporarily get your system to work (a new zypper dist-upgrade might fail, so be careful with that).
The cause was some ARM A53 errata handling:
–jeroen
Posted in *nix, *nix-tools, Development, DVCS - Distributed Version Control, git, Hardware Development, Linux, openSuSE, Power User, Raspberry Pi, Source Code Management, SuSE Linux, Tumbleweed | Leave a Comment »
Posted by jpluimers on 2018/01/11
Great set of tips; I’ve included to intro and ToC here so it’s easier for me to find, but all the details are at [WayBack] 19 Tips For Everyday Git Use. For each paragraph, the ToC lists the relevant command. The article itself also contains some very insightful animated images of which I included one below to get an impression.
Posted in Development, DVCS - Distributed Version Control, git, Source Code Management | 1 Comment »
Posted by jpluimers on 2017/12/31
A nice discussion followed on [WayBack] Senior Oops Engineer on Twitter: “what’s a blockchain?” It’s like git but for destroying the environment.
It basically comes down to: can alternatives like git together with a set of rules and contracts to facilitate upstream pushing to a global order of changes be sufficient alternative to the very resource intensive “calculate proof of work to achieve consensus”.
The discussion is at [WayBack] »”what’s a blockchain?” It’s like git but for destroying the environment.« – Kristian Köhntopp – Google+
References:
–jeroen
Posted in Development, DVCS - Distributed Version Control, git, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2017/11/15
When you haven’t pushed yet, git rebase --interactive HEAD~# where # is the number of commits to view is your friend: [WayBack] Changing a commit message – User Documentation.
At the first screen, replace aa with reword then change the commit message for each commit and copy the message.
Then in each following screen, if you changed the commit message for that commit, change it there as well.
Similar answers are at [WayBack] git – How to modify existing, unpushed commits? – Stack Overflow
–jeroen
Posted in Development, DVCS - Distributed Version Control, git, Source Code Management | Leave a Comment »
Posted by jpluimers on 2017/09/28
mention-bot (Mention Bot) is cool!
It mentions potential review users on a pull-request depending on the context (currently: if the users have lines deleted by the pull request or have enough blame presence around the modified lines in the pull request).
First saw it used here: https://github.com/libssh2/libssh2/pull/144#issuecomment-257244996
It has source code at facebook/mention-bot: Automatically mention potential reviewers on pull requests.
And there is mention-bot/how-to-unsubscribe
–jeroen
Posted in Continuous Integration, Development, DVCS - Distributed Version Control, git, GitHub, Power User, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2017/09/12
The Searching repositories – User Documentation mentions
By default, forked repositories are not shown.
But it forgets this only holds for the main search box which is conveniently called “Search GitHub” but documented as “Search repositories“:
Based on that documentation you’d think the “Search Repositories” box would adhere to the same defaults, right?
Wrong. We live in the “form over function” era so that would be too easy.
Posted in Development, DVCS - Distributed Version Control, git, GitHub, Source Code Management, User Experience (ux) | Leave a Comment »
Posted by jpluimers on 2017/08/30
From the “short git tips” department:
Try this:
git log --all -- path
Source: git – List all commits (across all branches) for a given file – Stack Overflow [WayBack]
–jeroen
Posted in Development, DVCS - Distributed Version Control, git, Source Code Management | Leave a Comment »
Posted by jpluimers on 2017/08/10
A great thread about Using BC4 OSX with Version Control Systems, -Tools and IDEs.
Some highlights:
–jeroen
Posted in Beyond Compare, CVS, Development, DVCS - Distributed Version Control, git, Mercurial/Hg, Power User, Software Development, Source Code Management, SourceTree, Subversion/SVN, TFS (Team Foundation System) | Leave a Comment »
Posted by jpluimers on 2017/08/08
For my link archive:
git push origin develop:master or $ git push <remote> <local branch name>:<remote branch to push into> can save your asstheirs and ours can be very confusing).–jeroen
Posted in Development, DVCS - Distributed Version Control, git, Software Development, Source Code Management | Leave a Comment »
The Wiert Corner - irregular stream of stuff 