I would say -1. Seems pointless to use another version control client that is not 100% compatible with SVN when the SVN command-line and UI clients works fine. What next, a mercurial read-only repository too? We have chosen to use subversion with MyFaces at Apache, I don't see any reason to support other clients just to appease some peoples technology fix. But this is just my opinion.
Note that there are tools out there to do this type of support from the client, not the server. For example, http://www.selenic.com/mercurial/wiki/WorkingWithSubversion details how to use Mercurial as an SVN client and even be able to commit to SVN! In my opinion, if someone wants to use git, then they should find a similar tool for git and not burden the folks at Apache. -Andrew FYI: http://www.russellbeattie.com/blog/distributed-revision-control-systems-git-vs-mercurial-vs-svn http://texagon.blogspot.com/2008/02/use-mercurial-you-git.html http://weblog.masukomi.org/2008/02/07/a-rebuttal-to-use-mercurial-you-git On Fri, May 15, 2009 at 10:45 AM, Matthias Wessendorf <mat...@apache.org> wrote: > some more infos: > > http://wiki.apache.org/general/GitAtApache > > On Fri, May 15, 2009 at 11:39 AM, Matthias Wessendorf <mat...@apache.org> > wrote: >> On Fri, May 15, 2009 at 11:37 AM, Werner Punz <werner.p...@gmail.com> wrote: >>> Matthias Wessendorf schrieb: >>> core >>>> >>>> Ok, I filed this: >>>> https://issues.apache.org/jira/browse/INFRA-2053 >>>> >>>> maybe we should also think about making the JSF 1.1.x stuff a branch ... >>>> (since we already work on 2.0.x....) >>>> >>> +1 >>> >>> 1.1.x branch >>> 1.2 trunk >>> 2.0 branch >> >> hehe :-) just wrote a similar email :-) >> >> -Matthias >> >>> >>> instead of >>> >>> 1.1 trunk >>> 1.2 trunk_1.2 >>> 2.0 branch >>> >>> this also helps the infrastructure people! >>> >>> >>> >>> >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf >
