9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Aram Hăvărneanu" <aram.h@mgk.ro>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] nix at lsub
Date: Mon, 16 Apr 2012 19:23:09 +0200	[thread overview]
Message-ID: <CAEAzY380ECzLQJCbNaK=QiYE6vzQpqTW3ZoakzW7EJ-WajptHg@mail.gmail.com> (raw)
In-Reply-To: <CAJVRB2VXZgWxAj_e-ZJ1HNKNWPYmuWPtpAD2bYYr9hiL2qruDQ@mail.gmail.com>

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...

-- 
Aram Hăvărneanu



  reply	other threads:[~2012-04-16 17:23 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-14 21:02 Nemo
2012-04-15 13:45 ` David Leimbach
2012-04-16 10:47 ` Francisco J Ballesteros
2012-04-16 11:02   ` Noah Evans
2012-04-16 17:23     ` Aram Hăvărneanu [this message]
2012-04-16 17:32       ` Noah Evans
2012-04-16 17:42         ` Noah Evans
2012-04-16 17:44         ` ron minnich
2012-04-16 20:53         ` Andrés Domínguez
     [not found]     ` <CAEAzY380ECzLQJCbNaK=QiYE6vzQpqTW3ZoakzW7EJ-WajptHg@mail.gmail.c>
2012-04-16 17:54       ` sl
2012-04-16 13:22   ` Christoph Lohmann
2012-04-16 18:04     ` Lucio De Re
2012-04-17  2:16 ` kokamoto
2012-04-17  5:53   ` andy zerger
2012-04-17  5:54     ` andy zerger
2012-04-17  7:17   ` Nemo
2012-04-17  8:41     ` kokamoto
2012-04-17  8:51       ` Francisco J Ballesteros
2012-04-17 12:22       ` Tristan
2012-04-17 18:56       ` Charles Forsyth
2012-04-17 19:13         ` Nemo
     [not found]         ` <charles.forsyth@gmail.com>
2012-04-18  0:26           ` kokamoto
2012-04-18  4:07             ` John Floren
2012-04-18  4:12               ` John Floren
2012-04-18  7:54             ` Francisco J Ballesteros
2012-04-18 12:27               ` Charles Forsyth
2012-04-18 12:35                 ` Francisco J Ballesteros
2012-04-18 15:45 arnold
2012-04-18 15:49 ` Francisco J Ballesteros
2012-04-18 16:09 arnold
2012-04-18 16:18 ` Nemo
2012-04-18 16:28   ` Charles Forsyth
2012-04-18 16:35     ` Francisco J Ballesteros
2012-04-18 17:43 ` Lucio De Re
2012-04-18 18:05 arnold
2012-04-19  1:37 ` hiro
2012-04-19  4:15   ` Jeff Sickel
2012-04-19  8:10     ` Charles Forsyth
2012-04-19  8:16       ` Joseph Stewart
2012-04-19  8:46         ` Charles Forsyth
2012-04-19 10:03           ` Bakul Shah
2012-04-19 10:32             ` Charles Forsyth
2012-04-19 16:36               ` Bakul Shah
2012-04-19 15:50 ` ComeauAt9Fans@gmail.com
2012-04-19 16:11   ` Lucio De Re
2012-04-19 17:09     ` ComeauAt9Fans@gmail.com
2012-04-19 17:56       ` Lucio De Re
2012-04-19 18:05         ` Comeau At9Fans
2012-04-19 18:23           ` Lucio De Re
2012-04-19 18:27           ` Lucio De Re

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAEAzY380ECzLQJCbNaK=QiYE6vzQpqTW3ZoakzW7EJ-WajptHg@mail.gmail.com' \
    --to=aram.h@mgk.ro \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).