Re:Why do you not make the code available under a 'source co...
by graycat on Wednesday June 17, 2015 @12:44PM
(#9733250)
My experience is that for a
software development project of
just a few people, for a
code repository fairly obvious use of
the hierarchical
file system on a shared server
is just fine.
[ Parent
| on HN ]
Re:Why do you not make the code available under a 'source co...
by s73v3r on Wednesday June 17, 2015 @01:18PM
(#9733572)
No, it isn't. Especially since it's so damn easy to setup a git or mercurial server.
Re:Why do you not make the code available under a 'source co...
by VLM on Wednesday June 17, 2015 @02:26PM
(#9734171)
Whats worse is most of the labor saving benefits like rollbacks, bisection, branch/merge all work just fine if you never type git push. Even just "what have I changed so far, oh git status". The client alone has many benefits.
Time for old guy rant that in the bad old days I just had a box I could ssh into and that was enough, or should I say, that was better than subversion. Don't forget to init the remote repo before pushing into it, as I forgot seemingly every single time. There was life before gitolite, gitlab, and github.
Re:Why do you not make the code available under a 'source co...
by plorkyeran on Wednesday June 17, 2015 @02:20PM
(#9734112)
I certainly thought that for a long time. Then I learned how to use version control.