Date: Wed, 21 Nov 2012 01:41:02 +0100 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Zach Leslie <xaque208@gmail.com> Cc: Alexander Yerenkow <yerenkow@gmail.com>, "C. P. Ghost" <cpghost@cordula.ws>, freebsd-hackers@freebsd.org, Volodymyr Kostyrko <c.kworr@gmail.com>, freebsd-security@freebsd.org, Ivan Voras <ivoras@freebsd.org>, freebsd-questions@freebsd.org Subject: Re: FreeBSD needs Git to ensure repo integrity [was: 2012 incident] Message-ID: <20121121004102.GQ71195@ithaqua.etoilebsd.net> In-Reply-To: <20121120030813.GB38037@zjl.local> References: <CAD2Ti29UoFcHendR8CcdQ4FPNW1HH0O47B1i3JW00Lke2m2POg@mail.gmail.com> <20121117221143.41c29ba2@nonamehost> <op.wnxq9eo0g7njmm@michael-think> <CADLo838oG26KmfHJ%2BtLh82GoJzzRtfqy69%2BNny1_DC8F8X4POQ@mail.gmail.com> <k8d914$ssl$1@ger.gmane.org> <50AA2A6C.8060604@gmail.com> <CADGWnjWgh%2BsWciS-XEA6SR6wukLdmqk0Hqr_Lrg5O2WGv9xyyw@mail.gmail.com> <CAOgwaMvjDshGByT9Qwk8tvVfundRJ8dVkZSchSNrMwTg4898wA@mail.gmail.com> <CAPJF9w=Z6a-o6wgk16zkckBTMFVaTCVWvUmDfYsQuV6aQMGotA@mail.gmail.com> <20121120030813.GB38037@zjl.local>
next in thread | previous in thread | raw e-mail | index | archive | help
--G6ArjEZjY3m60389 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 19, 2012 at 07:08:13PM -0800, Zach Leslie wrote: > > http://www.fossil-scm.org/ > >=20 > > I'm not fossil user, but it's BSD licensed in written in C. > > Baptise Daroussin probably could tell us more about fossil pro and cons. >=20 > This misses one of of the main points raised in the original post. The > proliferation of git as a revision control system. >=20 > Also, this particular tool bails out on the unix philosophy, with its web > gui, ticket tracker etc. Do one thing. Do it well. >=20 Look at the internal of fossil and how things are done in fossil and you wo= uld understand that the last sentence is totally wrong. Fossil has really nice features that could nicely fits with FreeBSD workflo= ws and greatly improves it. It has most of the new shiny feature everyone can expect from a dvcs, but it also has it drawbacks: The converted repositories (I did convert docs, src and ports) with full hi= story kept: branches, tags, etc. is huge and the first clone would be painful to = do. On the other side you have multiple working copies open on the same clone w= hich is really nice. Some of the operations can be slow, J=F6rg Sonnenberger wrote an analysis a= bout this one the fossil wiki, but don't remember the link sorry. =46rom my testing, apart from the do we really need a new scm question? I a= m a big fan of fossil and find it easier and cleaner than all the other scm I know,= I use git for pkgng and other projects, I use a lot mercurial on some other a= rea, and fossil remains my favorite :). But I really don't think it could fit FreeBSD's requirements as it is now. but there are lots of room of improvem= ents. The learning curve to fossil is probably really easy. On of the last thing is that fossil lacks keyword expansion. That said I'm happy with svn on FreeBSD, I still from time to time do conve= rsion of out different tree to fossil for fun, but no more and I won't advocate f= or any vcs change. Bapt --G6ArjEZjY3m60389 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlCsIx4ACgkQ8kTtMUmk6ExNdQCeOyKnCwMEgLgxzYvhc291sQen c3cAnjTrPoy2qLq4wd9QHtU+9zjb366B =eJAx -----END PGP SIGNATURE----- --G6ArjEZjY3m60389--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121121004102.GQ71195>