source code management
I'm still trying to write a program for my phone but I've already got lots of versions of it spread over various filesystems. My son has suggested that I use git and I see that there's an installable version for Mandriva. But before I go ahead and install it, is there anything I should know? I'm not particularly interested in storing the my source code online so I would like to have everything local, either on this 'ere machine or perhaps on a NAS drive. Is this the best approach though?
On 08/10/12 13:08, Chris Walker wrote:
I'm still trying to write a program for my phone but I've already got lots of versions of it spread over various filesystems.
My son has suggested that I use git and I see that there's an installable version for Mandriva. But before I go ahead and install it, is there anything I should know?
I'm not particularly interested in storing the my source code online so I would like to have everything local, either on this 'ere machine or perhaps on a NAS drive. Is this the best approach though?
Hi, I've used CVS, SVN/Subversion, Perforce and Git and have to say that I really like Git, once I got my mindset off the SVN style (I liked Perforce too, but that's most definitely not free). I'm using it with no issues on Mandriva and Kubuntu for both local and remote repositories. The potential advantage of hosting it on your NAS box would simply be that it's inherently backed-up (although one of the nice things about Git is that you can simply rsync a Git repo from one place to another and you've got a complete working copy, history 'n' all). Git's also built to work much better off-line (certainly compared to, say, SVN), so you're not blocked by choosing to host your "main" repo on your NAS if it's not available for some reason. You don't need network access to commit changes, diff against previous versions or show history, etc, you only it to "push" any pending commits to a remote repo or to "pull" (update) if you're collaborating with someone else. If you don't want to host on your NAS, you could still clone a separate working copy from your main source code stash on your own machine in case you're worried about completely stuffing everything up and you want to start again. Not sure what else to say about it, other than if you have any previous code-versioning experience it can be a little confusing at first - it has different meanings for terms other versioning systems use, like "commit", and it has strange-at-first terms like "fast forwarding". I've had fewer problems managing/merging branches than any other system, and its lack of network dependency comes in handy when working on the train when the WiFi's a bit dodgy. Hope that helps, Simon -- ----------------------------------------------------------- Simon Ransome web: http://nosher.net/ rss: http://nosher.net/images.rss
On Mon, Oct 08, 2012 at 03:40:58PM +0100, Simon Ransome wrote:
collaborating with someone else. If you don't want to host on your NAS, you could still clone a separate working copy from your main source code stash on your own machine in case you're worried about completely stuffing everything up and you want to start again.
That's basically what I do with git on my system. The git repository gets backed up anyway with my main backups (to the NAS in the garage). -- Chris Green
git and Mercurial are both based on similar principles (distributed version control systems). I found when I did a comparison a few years back that Mercurial did tend to have a more consistent interface and the tools were somewhat easier for new users (particularly Windows) to pick up, for the community I support. Wha clinched it was a comment I read from one of the original authors of the O'Reilly book on Subversion who works for Google, who made it clear that he uses Mercurial exclusively for his non-work projects. That said, they'll both do the job ... hginit.com is a good place to start with Mercurial. Peter.
On Mon, Oct 08, 2012 at 01:08:31PM +0100, Chris Walker wrote:
I'm still trying to write a program for my phone but I've already got lots of versions of it spread over various filesystems.
My son has suggested that I use git and I see that there's an installable version for Mandriva. But before I go ahead and install it, is there anything I should know?
I'm not particularly interested in storing the my source code online so I would like to have everything local, either on this 'ere machine or perhaps on a NAS drive. Is this the best approach though?
I use git locally on my machine here at home to keep control of all the bits and pieces I write (mostly bash and python scripts but also some others). As long as you can remember to commit changes fairly regularly it is a big help when trying to see where something changed/broke etc. -- Chris Green
Hi Chris, I personally use Git on https://bitbucket.org/ as they provide a free plan with unlimited repositories. They support both Git and Mercurial so you can try your hand at both. I haven't had any experience of running these systems internally but would love to try my hand at developing a CI Server with a local git instance and Mocha testing on any commits, so please let us know your experience if you do try setting up your own git server. I would suggest Bitbucket though and you get the added bonus of a backup of your code on a remote git server. I commit every line of code to git now, wouldn't want to code without it! HTH Alex On Mon, Oct 8, 2012 at 5:04 PM, Chris Green <cl@isbd.net> wrote:
On Mon, Oct 08, 2012 at 01:08:31PM +0100, Chris Walker wrote:
I'm still trying to write a program for my phone but I've already got lots of versions of it spread over various filesystems.
My son has suggested that I use git and I see that there's an installable version for Mandriva. But before I go ahead and install it, is there anything I should know?
I'm not particularly interested in storing the my source code online so I would like to have everything local, either on this 'ere machine or perhaps on a NAS drive. Is this the best approach though?
I use git locally on my machine here at home to keep control of all the bits and pieces I write (mostly bash and python scripts but also some others).
As long as you can remember to commit changes fairly regularly it is a big help when trying to see where something changed/broke etc.
-- Chris Green
_______________________________________________ main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
participants (5)
-
Alex Scotton -
Chris Green -
Chris Walker -
samwise -
Simon Ransome