On Thu, Jun 25, 2009 at 3:38 AM, Pierre Ossman <oss...@cendio.se> wrote:
> On Wed, 24 Jun 2009 13:24:53 -0500 > DRC <dcomman...@users.sourceforge.net> wrote: > > > We've had this discussion before, and the reasons we chose SVN are: (a) > > SourceForge supports it, so we can keep the repository on our SF page, > > (b) it was a system we all knew how to use, and (c) it's a system that > > most people in the OSS community know how to use as well. > > (a) no longer applies as Sourceforge supports git these days actually. > > I'd really like to use git here as I agree with Adam that it is a far > superior tool. But I also agree with DRC. If changing tools causes one > of our (few) developers to be unable to contribute, then it is not the > right time to change. > > I believe that git is something that every free software developer > needs to learn eventually though as a lot of projects are moving to it, > and I do hope you'll find the time to learn it soon. > > Rgds > -- > Pierre Ossman OpenSource-based Thin Client Technology > System Developer Telephone: +46-13-21 46 00 > Cendio AB Web: http://www.cendio.com > Since SourceForge now supports Git, Bazaar, Mercurial, and SVN, why not have them mirrored against each other? If someone pushes a commit into Git, it would be mirrored into a Bazaar, Mercurial, and SVN repo, and if someone does it into SVN, it goes into the rest of them and so on and so forth. It might be a bit difficult to set up, but this would satisfy everybody. Of course, we don't have to support ALL of the DVCSes, just pick one or two that SF supports. Obviously quite a few of the Linux people like Git, so picking either Mercurial or Bazaar for DVCS support to non UNIX users should be easy.
------------------------------------------------------------------------------
_______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
