|
»
»
Move to Subversion?
|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
 |
Move to Subversion?
by Bugzilla from bluelightning@bluelightning.org
::
Rate this Message:
Hi all,
Is there any chance of us being able to convert from CVS to Subversion? CVS is rather painful to deal with these days. Cheers, Paul _______________________________________________ http://opie.handhelds.org/cgi-bin/moin.cgi/DeveloperWikiIndex Opie-devel mailing list Opie-devel@... https://handhelds.org/mailman/listinfo/opie-devel |
|
|
Re: Move to Subversion?
by Erik Hovland
::
Rate this Message:
On Sat, Aug 25, 2007 at 05:03:45PM +1200, Paul Eggleton wrote:
> Hi all, > > Is there any chance of us being able to convert from CVS to Subversion? CVS is > rather painful to deal with these days. I don't have a problem with this. But with development being only a few people, I don't see what makes cvs painful. E -- Erik Hovland mail: erik@... web: http://hovland.org/ PGP/GPG public key available on request _______________________________________________ http://opie.handhelds.org/cgi-bin/moin.cgi/DeveloperWikiIndex Opie-devel mailing list Opie-devel@... https://handhelds.org/mailman/listinfo/opie-devel |
|
|
Re: Move to Subversion?
by Bugzilla from bluelightning@bluelightning.org
::
Rate this Message:
On Sat, 25 Aug 2007, Erik Hovland wrote:
> I don't have a problem with this. But with development being only a few > people, I don't see what makes cvs painful. The current number of developers is not significant - we're still talking centralised version control here. When you've worked with Subversion a lot (as I have) being forced to use CVS again is definitely painful. Subversion has local change tracking, repository-wide versioning, easy reverts, and transactioned commits. These are things that you come to rely on and miss very much when they arent there. Not to mention that it is faster as well. I'm suggesting the move because I think it makes development easier, and because the transition from CVS to Subversion is a fairly easy one - both in terms of usage and in converting the repository data. Cheers, Paul _______________________________________________ http://opie.handhelds.org/cgi-bin/moin.cgi/DeveloperWikiIndex Opie-devel mailing list Opie-devel@... https://handhelds.org/mailman/listinfo/opie-devel |
|
|
Re: Move to Subversion?
by Erik Hovland
::
Rate this Message:
On Sat, Aug 25, 2007 at 09:41:42PM +1200, Paul Eggleton wrote:
> On Sat, 25 Aug 2007, Erik Hovland wrote: > > I don't have a problem with this. But with development being only a few > > people, I don't see what makes cvs painful. > > The current number of developers is not significant - we're still talking > centralised version control here. > > When you've worked with Subversion a lot (as I have) being forced to use CVS > again is definitely painful. Subversion has local change tracking, > repository-wide versioning, easy reverts, and transactioned commits. These > are things that you come to rely on and miss very much when they arent there. > Not to mention that it is faster as well. > > I'm suggesting the move because I think it makes development easier, and > because the transition from CVS to Subversion is a fairly easy one - both in > terms of usage and in converting the repository data. What about another model all together, like git. E -- Erik Hovland mail: erik@... web: http://hovland.org/ PGP/GPG public key available on request _______________________________________________ http://opie.handhelds.org/cgi-bin/moin.cgi/DeveloperWikiIndex Opie-devel mailing list Opie-devel@... https://handhelds.org/mailman/listinfo/opie-devel |
|
|
Re: Move to Subversion?
by Bugzilla from bluelightning@bluelightning.org
::
Rate this Message:
On Sun, 26 Aug 2007, Erik Hovland wrote:
> What about another model all together, like git. I don't have any direct experience with git, or any distributed system for that matter. I've read what Linus has to say about it and I'm sure it works well when you have lots of different groups wanting to do different things in the source tree, but for a small team such as ours does it make sense? What benefits would we get in exchange for having to learn a whole new system? Is there a way to import CVS history into git? Cheers, Paul _______________________________________________ http://opie.handhelds.org/cgi-bin/moin.cgi/DeveloperWikiIndex Opie-devel mailing list Opie-devel@... https://handhelds.org/mailman/listinfo/opie-devel |
|
|
Re: Move to Subversion?
by Erik Hovland
::
Rate this Message:
On Sun, Aug 26, 2007 at 03:21:44AM +1200, Paul Eggleton wrote:
> On Sun, 26 Aug 2007, Erik Hovland wrote: > > What about another model all together, like git. > > I don't have any direct experience with git, or any distributed system for > that matter. I've read what Linus has to say about it and I'm sure it works > well when you have lots of different groups wanting to do different things in > the source tree, but for a small team such as ours does it make sense? Well, it would be more in line with my development process. Currently I maintain a quilt repo on top of cvs and only push patches when I consider them ready. Obviously, I could just keep doing that with svn (I currently do that with amarok). > What benefits would we get in exchange for having to learn a whole new > system? Admittedly very little. > Is there a way to import CVS history into git? Yes, just like with svn. For that matter, there is a way to use git w/ svn and there is a way to import svn into git. So I only ask these questions to make sure we have explored our options. E -- Erik Hovland mail: erik@... web: http://hovland.org/ PGP/GPG public key available on request _______________________________________________ http://opie.handhelds.org/cgi-bin/moin.cgi/DeveloperWikiIndex Opie-devel mailing list Opie-devel@... https://handhelds.org/mailman/listinfo/opie-devel |
|
|
Re: Move to Subversion?
by Bugzilla from bluelightning@bluelightning.org
::
Rate this Message:
On Sun, 26 Aug 2007, Erik Hovland wrote:
> Well, it would be more in line with my development process. Currently I > maintain a quilt repo on top of cvs and only push patches when I > consider them ready. Obviously, I could just keep doing that with svn (I > currently do that with amarok). Maintaining private trees is a definite advantage of git and other distributed systems, no doubt about it. I does seem like git-svn would allow you to do this fairly easily on top of svn though - the best of both worlds. > So I only ask these questions to make sure we have explored our options. Of course :) Cheers, Paul _______________________________________________ http://opie.handhelds.org/cgi-bin/moin.cgi/DeveloperWikiIndex Opie-devel mailing list Opie-devel@... https://handhelds.org/mailman/listinfo/opie-devel |
|
|
|
| Free embeddable forum powered by Nabble | Forum Help |
