Beefy Boxes and Bandwidth Generously Provided by pair Networks Ovid
Your skill will accomplish
what the force of many cannot
 
PerlMonks  

Re: Unrelated scripts and version control

by lima1 (Curate)
on Sep 23, 2010 at 14:47 UTC ( #861562=note: print w/ replies, xml ) Need Help??


in reply to Unrelated scripts and version control

One of the things I like about git is that it is easy and fast to set up a local repository. You have a small script and decide it would be nice to try a couple of things. Then just run git init and you have your local version control in your script directory. If you later want to collaborate, it's easy to clone the repository wherever you want. If you add the script to your one big SVN repository, it's there forever.

I mean, for small things and finished projects, how often do you really need the version history? In git it's just this .git folder in your project directory. I didn't experience an administration overhead since my switch.


Comment on Re: Unrelated scripts and version control
Re^2: Unrelated scripts and version control
by loris (Hermit) on Sep 24, 2010 at 07:06 UTC

    Just running git init to create a local repository is obviously not such a big deal. However, if I want to collaborate with my colleagues, I have to set up a corresponding bare repository on a server that I can then push to. Doing this for a couple of dozen individual scripts seems like it might be unmanagable overkill.

    Regarding the history, I do want this for individual files and I don't have such things as "finished" projects. I mainly have stuff for myself, which either contains bugs or is not as good as it could be, or both.

    Perhaps I just need to try working with a small number of repositories and see how it feels. I gather that can always merge them at some later point.

    Cheers,

    loris

      As I said, I didn't experience an overhead. In SVN, you normally need one step to prepare the directory for SVN import (e.g. the trunk/ branch/ merge directory structure) which somehow would correspond to git init. To publish it, svn import would correspond to git clone -bare.

      Your couple of dozen scripts are all unrelated? So there is no group of scripts your colleagues would likely want to fetch together?

      What I meant with my history comment was, I also used to have a single big SVN repository for almost everything. My SVN dump was huge at the end. But for most projects, I never actually needed the history later on. Now I have a decent backup system and git when version control is actually needed (collaboration, branching etc.). So much cleaner and better...

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://861562]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others romping around the Monastery: (9)
As of 2014-04-24 10:28 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    April first is:







    Results (565 votes), past polls