I argue that using a source control system of any kind is useful for answering the questions like "This was working 6 months ago. What have I changed since then?" or "This line of code to work around feature X is odd. When did I change it and what was my motivation at the time?"
Git has the advantage that it doesn't require a server to track the commits for a single person so you could just use it on a local filesystem with normal file-level backups. That would reduce the complexity quite a bit. Brian Oborn On Tue, Dec 19, 2017 at 10:11 AM, Faraz Hussain <i...@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@beowulf.org sponsored by Penguin Computing > To change your subscription (digest mode or unsubscribe) visit > http://www.beowulf.org/mailman/listinfo/beowulf >
_______________________________________________ Beowulf mailing list, Beowulf@beowulf.org sponsored by Penguin Computing To change your subscription (digest mode or unsubscribe) visit http://www.beowulf.org/mailman/listinfo/beowulf
