on Gitorious and cvs

From: Daniel Black <daniel.subs_at_internode.on.net>
Date: Wed, 21 Oct 2009 12:54:54 +1100

On Wednesday 21 October 2009 03:36:12 Murray S. Kucherawy wrote:

> What does gitorious offer that isn't available with things like "cvs log"
> and "cvs annotate"?

The ability for non-developers, like myself, to generate a clone of the
repository and treat it as their own, and then run wild with code changes for
a few days or weeks.

The advantages are is the:
1. repository clones hosted on gitorious are visible on so you can sort of see
what ideas people are coming up with.

2. repository clones are full repositories in the own right allowing anyone
with an itch to grab a copy easily and do their own version controlled work
(just requires a few web page clicks or a single command line command).

3. merge requests allow developers to say here's a patch that gets directly
imported, after approval, with all commit history. The developer's requesting
the merge request just select the right bit of code out of their git clone so
its a little less fiddly on their part. I assume approval of merge requests is
a one click accept and its in the repository.

4. the visibility of branches is very clear to try out new features and the
merge it back in when complete.

5. picking out commit URLs is pretty easy

6. good status page

Other things I've found useful:
1. gitorious servers are very fast to do git pushes (aka cvs commits)
2. there is a comment feature available on all commits
3. wiki included
4. very scalable to even large scale development, like Qt,

useful features of git over cvs are:
1. renames of files keep history
2. can stage offline commits without any extra effort

Note: some of these may be derived from my long but really only basic
experience with cvs.
Received on Wed Oct 21 2009 - 01:55:13 PST

This archive was generated by hypermail 2.3.0 : Mon Oct 29 2012 - 23:32:29 PST