From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: From: =?UTF-8?B?QXJhbSBIxIN2xINybmVhbnU=?= Date: Mon, 16 Apr 2012 19:23:09 +0200 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] nix at lsub Topicbox-Message-UUID: 76dc23cc-ead7-11e9-9d60-3106f5b1d025 Noah Evans wrote: > To clarify, Nix development will be continuing at both > nix-dev@googlegroups.com and http://code.google.com/p/nix-os as well. > The project has forked. I don't understand what is going on. I though some people were very unsatisfied with the rietveld code review tool offered by Google Code, and Nemo created some new tools to be used instead of rietveld and mercurial. Of course Nemo's tools don't work with Google Code hosting so the project is moved at lsub, and by design the old mailing list, nix-dev@googlegroups.com, is tied with the Google Code project, so a new mailing list has to be used instead. So what's this fork I'm hearing about? Someone wants to maintain the mercurial repository independent of the work done at lsub? Who? Why? If this is not the case, and I hope it isn't, destroy the Google Code project. Delete it, there's no point for this confusion. Personally I would have preferred that the mercurial repository would have remained the place where nix development would happen. I believe the problems people felt with rietveld could be solved by running a private instance of rietveld, instead of the generic one at Google, but whatever, I have no say in this. Just keep it in one place if there's no schism happening. So what's happening? John's message on nix-dev@ adds more to this confusion= ... --=20 Aram H=C4=83v=C4=83rneanu