Since I tend to forget the exact statements for starting a fresh repository and push it to a git hoster like GitHub or GitLab: [WayBack] Git: Push a new or existing repo to Github · GitHub
–jeroen
Archive for the ‘DVCS – Distributed Version Control’ Category
Git: Push a new or existing repo to Github · GitHub
Posted by jpluimers on 2019/11/27
Posted in Development, DVCS - Distributed Version Control, git, GitHub, GitLab, Software Development, Source Code Management | Leave a Comment »
Unorthodocs: Abandon your DVCS and Return to Sanity – bitquabit
Posted by jpluimers on 2019/11/21
Some interesting thoughts on DVCS: [WayBack] Unorthodocs: Abandon your DVCS and Return to Sanity – bitquabit
Besides the very good point it raises about DVCS (Git, Mercurial and most other DVCSes treat the whole state of the repository as the atom) it also indicates quite a few shortcomings:
- most people hardly ever need the full history to be off-line
- having the full history means repositories get huge in size, including your off-line clone
- pseudo-solutions for huge repository sizes – like git-LFS or git-annex – are a no-go because now you loose atomicity
- huge repositories in file or commit counts make them slow, especially when the trees are deep
- splitting up repositories isn’t a good idea either because again: you loose atomicity
- all DVCS are hard, not just git, because they are distributed and full of features
- the workflow for submitting pull requests is quite a bit longer than submitting a patch, even though merging in a DVCS can be hard too (despite atomicity which does help a lot for DVCS systems)
I see many other advantages of DVCS systems (for instance that you only need to locally have the branches you are interested in, way better tooling for DVCS systems, ditto for sites hosting DVCS), but it always a good thing to know the weak spots of what you are working with.
–jeroen
Share this:
Posted in Development, DVCS - Distributed Version Control, git, Mercurial/Hg, Software Development, Source Code Management | Leave a Comment »
git tag – How to delete a git remote tag? – Stack Overflow
Posted by jpluimers on 2019/11/20
When working with git, often the brevity of a solution is remarkable. Remembering how it can be so short is the hard part. An explanation why helps, for instance with [WayBack] git tag – How to delete a git remote tag? – Stack Overflow by markdorison.
He explains why you end up with:
git push --delete <origin> <tagname>
Here, <origin> is your remote, and <tagname> the tag to delete.
He explains other ways, which is done by [WayBack] gist.github.com/mobilemind/7883996 as well:
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # delete local tag '12345' | |
| git tag -d 12345 | |
| # delete remote tag '12345' (eg, GitHub version too) | |
| git push origin :refs/tags/12345 | |
| # alternative approach | |
| git push –delete origin tagName | |
| git tag -d tagName |
–jeroen
Share this:
Posted in Development, DVCS - Distributed Version Control, git, Software Development, Source Code Management | Leave a Comment »
Gitless: a simple version control system built on top of http://gitless.com/
Posted by jpluimers on 2019/10/09
Time to experiment with [WayBack] Gitless: a simple version control system built on top of http://gitless.com/:
…
Gitless is an experiment to see what happens if you put a simple veneer on an app that changes the underlying concepts. Because Gitless is implemented on top of Git (could be considered what Git pros call a “porcelain” of Git), you can always fall back on Git.
…
It is open source at https://github.com/sdg-mit/gitless
–jeroen
Share this:
Posted in Development, DVCS - Distributed Version Control, git, Software Development, Source Code Management | Leave a Comment »
Git man-page generator (“Git is easy to learn”)
Posted by jpluimers on 2019/10/08
Somebody didn’t believe the claim “Git is easy to learn” and wrote a [WayBack] git man page generator (of course with a repository: github: Lokaltog/git-man-page-generator), for example generating
git-complete-tipNAME
git-complete-tipcomplete all non-committed downstream tips opposite of a few rebased remote indicesSYNOPSIS
git-complete-tip[ –maintain-log | –lecture-violate-history ]DESCRIPTION
git-complete-tipcompletes a few staged tips inside any forward-ported non-staged unstaged indices, and a few checked out subtrees fscked by histories in the tree, but that are not inHOLD_SUBTREE, are checked out in a temporary pack.…
For the same reason there is [WayBack] XKXD: Git (image on the right), which is [WayBack] explained for a reason. Just see this little summary:
The difficulty of using Git in common situations is belied by the apparent simplicity of its use in tutorial-style situations. Committing and sharing changes is fairly straightforward, for instance, but recovering from situations such as accidental commits, pushes or bad merges is difficult without a solid understanding of the rather large and complex conceptual model. For instance, three of the top five highest voted questions on Stack Overflow are questions about how to carry out relatively simple tasks: undoing the last commit, changing the last commit message, and deleting a remote branch.
Actually the “easy to learn” means “there is easy to find documentation for it“.
–jeroen
Share this:
Posted in Development, DVCS - Distributed Version Control, Fun, git, Software Development, Source Code Management | Leave a Comment »
Fork – a fast and friendly git client for Mac
Posted by jpluimers on 2019/09/24
Works for Windows too: [WayBack] Fork – a fast and friendly git client for Mac.
Via [WayBack] Weekend Reader 2017.46 – reality-loop(who switched away from SourceTree, because, well, that was ahead of it’s time but in the end couldn’t keep up with reality)
–jeroen
Share this:
Posted in Development, DVCS - Distributed Version Control, git, git-fork, Software Development, Source Code Management, SourceTree | Leave a Comment »
git add remote with tracking
Posted by jpluimers on 2019/08/27
Since I keep forgetting this and the top search for “git remote add” “tracking” do not answer it (see for instance …):
git remote add gitlab https://user@gitlab.com/group/subgroup/repository.git -t master
This adds a new gitlab remote on the repository path https://user@gitlab.com/group/subgroup/repository.git tracking branch master.
–jeroen
Share this:
Posted in Development, DVCS - Distributed Version Control, git, Source Code Management | Leave a Comment »
Some git versus PlasticSCM comparisons
Posted by jpluimers on 2019/08/01
Via a co-worker:
- [WayBack] Plastic SCM – Plastic SCM for Git Users How to move from Git and what Plastic offers you: support for large files, consistent GUIs, handles huge repos, semantic diffing and merging, and more.
- [WayBack] Plastic SCM vs Git – Pablo Santos – Medium
- [WayBack] Plastic SCM blog: Why we don’t delete branches in Plastic?
In my own experience, PlasticSCM needs a lot of work, especially on the usability side:
- PlasticSCM call themselves a DVCS, but in order to have a local full repository like all other DVCS systems, you have to run a local server (and a license for it, I still need to sort out if that is free or paid). For the DVCS definition, see Distributed version control – Wikipedia. This means you run a client, a local PlasticSCM server and a remote PlasticSCM server.
- Despite there being a CLI version (more on that in a future post), the GUI does not show the exact CLI syntax for commands (unlike most git tools that do). This means you need to think thrice when translating them from GUI to CLI, made even harder by most UI access paths having different ways to copy their information to the clipboard.
- When you run the Plastic SCM GUI client long enough, even on a small repository, you will get errors about not enough quota being available (the dreaded 0x718): [WayBack] System Error Codes (1700-3999) | Microsoft Docs
ERROR_NOT_ENOUGH_QUOTA1816 (0x718): Not enough quota is available to process this command. - Often after scanning for changes, you see a lot of changed files. If you click each file, you see “Files are identical”
- As a result you have to perform “Undo Unchanged”:
- I never have this when using git.
- As a result you have to perform “Undo Unchanged”:
- Online PlasticSCM hosting parties, especially integrated with bug tracking, are far and few between: besides [WayBack] PlasticSCM cloud, I have not found any. Take the git world, or even the Mercurial world and there are far more choices (yes I know about the manual labour involved setting it up described at [WayBack] Plastic SCM version control · Task and issue tracking systems guide and [Archive.is] Plastic SCM blog: Integrating Plastic SCM with Trac Issue Tracking).
One thing that baffled me is that you can edit commit messages. Changing them does not result in another commit. This means that these are not set in stone which is very odd when you see all changes in the commit history.
[Archive.is] Are check-in comment editable?
Sure!
The commit message textbox is editable, start typing and then push save.
—
I realized that in the Branch Explorer one can edit them using the procedure you’ve described, but if you open a changset from “Changesets” or somewhere else, the comment on the top is readonly. Maybe it would be nice to be have a way to edit it there, though I guess, it would be a rarely used feature.
—
At the changesets view you are also able to do it by cliking in the “Show extended information” button.
I’m afraid that this are the only spots to do it.
–jeroen
Share this:
Posted in Development, DVCS - Distributed Version Control, git, Source Code Management | Leave a Comment »
How to test if an executable exists in the %PATH% from a windows batch file? – Stack Overflow
Posted by jpluimers on 2019/06/20
I needed a solution inside a batch file for git similar to [WayBack] How to test if an executable exists in the %PATH% from a windows batch file? – Stack Overflow which became this:
where /q git || echo Cound not find git on the PATH %PATH%. && goto :eof
I could have expanded this to find the install location, but for now this is sufficient.
When it is needed, I should read [WayBack] Programmatically (not manually) finding the path where Git is installed on a Windows system – Stack Overflow
–jeroen
Share this:
Posted in Batch-Files, Development, DVCS - Distributed Version Control, git, Scripting, Software Development, Source Code Management | Leave a Comment »
Githunt – Chrome Web Store – discover new github projects in your technology area of interest
Posted by jpluimers on 2019/06/10
Archive.is Githunt – Chrome Web Store: Replace the new tab with a list of trending repositories on github belonging to any technology that you chose.
More information: [WayBack] How to get trending GitHub projects in your Chrome new tab screen with GitHunt
–jeroen
via: [WayBack] This is how I discover new and interesting open source Delphi/Pascal projects – install Githunt and it replaces my ‘new tab’ page, there I set the langu… – Edwin Yip – Google+
Share this:
Posted in Development, DVCS - Distributed Version Control, git, GitHub, Software Development, Source Code Management | Leave a Comment »
The Wiert Corner - irregular stream of stuff 