Official git export

[Vadim Goncharov]

Hi Robert Watson! 

On Fri, 26 Aug 2011 10:06:32 +0100 (BST); Robert Watson wrote about 'Official git export (was: Re: FreeBSD problems and preliminary ways to solve)':

> One way to do this is to make "more official" our output if git exports of the 
> repository -- something that many other Subversion-based projects do: 
> Chromium, clang/LLVM, Tor, etc.  Folk like Ulrich have been doing this on a 
> casual basis for some time, but I think we need to formalise this and provide 
> end-user documentation on how to use git to track FreeBSD, contribute patches, 
> etc.  There are a number of hitches people have to know about: the potential 
> impact of obliteration, how to handle $FreeBSD$ correctly for system call 
> additions, and so on.  Simply writing them down and having an official 
> git.FreeBSD.org (or even gitsvn.FreeBSD.org) would go a long way.

Is it only the git what is considered? Mercurial (hg) has a plugin for $Id$
conversion and is popular enough, too.

> I have to admit I've always preferred Perforce to git, simply because it 
> strikes me as a more structured approach, partial checkouts (but especially 
> composition of different depot pieces in a single checkout to create hybrid 
> trees), etc.  But git is widely used, and quite effectively used, by large 
> communities.  We need to support those communities better.

I haven't worked with Perforce, do you mean I could checkout at once several
directories e.g. sbin/ipfw and sys/netinet/ipfw in my working copy? If so,
sounds good. May be FreeBSD should really write it's own VCS, just as Git was
modelled after proprietary BitKeeper?..

-- 
WBR, Vadim Goncharov. ICQ#166852181       mailto:vadim_nuclight at mail.ru
[Anti-Greenpeace][Sober FreeBSD zealot][http://nuclight.livejournal.com]