Posted by jpluimers on 2019/11/04
For my history: [WayBack] Jeroen Pluimers on Twitter: “How can I view a file in the @plasticscm webUI? I tried from changeset view, but clicking on a file does nothing. When looking in the Chrome developer tools, I see an error 500 which is not surfaced to the UI.…
Images:
–jeroen
Posted in Development, PlasticSCM, Source Code Management | Leave a Comment »
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
Posted in Development, DVCS - Distributed Version Control, git, Software Development, Source Code Management | Leave a Comment »
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
Posted in Development, DVCS - Distributed Version Control, Fun, git, Software Development, Source Code Management | Leave a Comment »
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
Posted in Development, DVCS - Distributed Version Control, git, git-fork, Software Development, Source Code Management, SourceTree | Leave a Comment »
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
Posted in Development, DVCS - Distributed Version Control, git, Source Code Management | Leave a Comment »
