Date: Tue, 30 Aug 2011 21:47:40 +0000 (UTC) From: Vadim Goncharov <vadim_nuclight@mail.ru> To: freebsd-arch@freebsd.org Subject: Re: Official git export Message-ID: <slrnj5qmjr.17m0.vadim_nuclight@kernblitz.nuclight.avtf.net> References: <35765857-1314243257-cardhu_decombobulator_blackberry.rim.net-329610575-@b2.c15.bise7.blackberry> <CAJ-Vmo=v0UkQarauKrvWKdjMTC81BwXmyhU__rnaQeL3z45L-g@mail.gmail.com> <slrnj5ddgp.4ck.vadim_nuclight@kernblitz.nuclight.avtf.net> <CAMBSHm8uX45k0M4on=5Cpw_CKoddA=4oJSNXpH7dGPt=Vy2HOw@mail.gmail.com> <alpine.BSF.2.00.1108261000040.48200@fledge.watson.org> <slrnj5lc58.jd1.vadim_nuclight@kernblitz.nuclight.avtf.net> <3CE7269E-DDD8-4A28-9FCD-D8FEA3C89089@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Philip Paeps! On Mon, 29 Aug 2011 14:39:46 +0200; Philip Paeps wrote about 'Re: Official git export': >>> 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. > Yes. Perforce is 'namespace-based'. You map parts of the repository namespace > into your client namespace and work from there. Branches are free for most > practical purposes and it's reasonably easy to merge between branches. Sounds very cool for Joe Random Contributor. > The main downside of Perforce is that the server likes to track every client's > files and that things get very shaky when you try to interfere with that > principle. One of my customers uses Perforce without tracking (or tries to) > and it goes horribly wrong in a number of ways (gigantic "p4 have" databases, > which don't reflect reality, accidental "p4 sync -k" locking up the server > for everyone for hours,...). That's not cool. I've already prepared to ask how to gain access and use for Joe Random Contributor... :-/ >> May be FreeBSD should really write it's own VCS, just as Git was >> modelled after proprietary BitKeeper?.. > I think git is a very reasonable system and it should be possible to map the > way we work with FreeBSD into git. As has been mentioned elsethread: things > would be a lot easier if we had "official git seeds" to pull from which > would make it easy to collaborate and then push things up into SVN. Also, a > page of "rules for things not to do with git" would be helpful. It would be > a bad idea if committers using git pushed changes into Subversion which made > subversion impossible to use (or much harder to use than it currently is). If the question is "make git officially additional to SVN", I'll vote for it. If the question is "replace SVN completely with Git", then I'll strongly object and better vote for writing FreeBSD's own VCS. -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nuclight@mail.ru [Anti-Greenpeace][Sober FreeBSD zealot][http://nuclight.livejournal.com]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?slrnj5qmjr.17m0.vadim_nuclight>