[Beowulf] Thoughts on git?
Lux, Jim (337K)
james.p.lux at jpl.nasa.gov
Tue Dec 19 17:45:09 PST 2017
The problem with git is that it wasn’t “architected”, it just sort of grew to meet a variety of needs. So the commands don’t necessarily make sense, and there are multiple ways to achieve a particular desired end result, particularly in a simple environment. (
And, of course, like any other source code control system, the commands and terminology are different for git than every other SCCS.
Most projects wind up issuing a set of “here’s how WE are doing these 5 things in git” with cookbook sets of commands for the things that everybody does on a day to day basis.
On 12/19/17, 8:11 AM, "Beowulf on behalf of Faraz Hussain" <beowulf-bounces at beowulf.org on behalf of info at feacluster.com> wrote:
I am curious what people think of git. On one hand everyone seems to
be using it and proclaiming its virtues. On the other hand it seems
way overkill for how the majority of people code.
I maintain dozens of scripts to manage various HPC environments . None
are more than a few hundred lines long. To do backups of scripts, I
just copy them to some backup folder. Occasionally I might tar them up
and copy them to a different server. I have never had a need to go
back to an older version of my script.
So I tried to learn git but find it very confusing. It seems designed
for teams of developers working on some million+ line of code project.
For my rinky-dinky scripts it just adds a lot of confusion. It seems I
need to "commit" to using git everyday in order for it to be
effective. Otherwise, use it or lose it.
Should I force myself to use git everyday? Or maybe find some
incrementally better way to manage backups of my scripts?
Beowulf mailing list, Beowulf at beowulf.org sponsored by Penguin Computing
To change your subscription (digest mode or unsubscribe) visit http://www.beowulf.org/mailman/listinfo/beowulf
More information about the Beowulf