From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <9bef3191d2c415d1031b0d3dc02aebfb@proxima.alt.za> Date: Wed, 21 May 2014 09:56:26 -0700 Message-ID: From: Skip Tavakkolian To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a11c322468f5abb04f9ebe09f Subject: Re: [9fans] syscall 53 Topicbox-Message-UUID: eae8c79c-ead8-11e9-9d60-3106f5b1d025 --001a11c322468f5abb04f9ebe09f Content-Type: text/plain; charset=UTF-8 i like git. as it is a kind of archival file system, one should be able to build a plan9 file system interface for it. On Wed, May 21, 2014 at 9:25 AM, erik quanstrom wrote: > > I think such a beast would provide the foundations for a serious > > effort to bring the distributions back together. I know many resist > > such efforts because of Python (a pet hate of mine, even though I > > don't know it from Adam), HG and codereview and I resist accusing them > > of reactionary behaviour; I do wish we could get past that problem, > > though. > > fwiw... > > i use a derivative of nemo's patch system. all changes are applied through > patches. anyone can comment on a patch, and comments, and patch > dispositions are mailed to everyone on the list. the list is open to > general discussion. the patch system allows folks to pull (not > executables) > or apply patches themselves, so in spirit it's closer to git than hg. > > i'm open to any sort of gateway to hg/codereview/git that folks find > useful. > i just don't want hg to be a requirement. one of the things i value about > plan 9 is the fact that it's a self-contained system. requiring hg and > websites > runs counter this. i haven't carved out the time to do anything about it, > but patches are welcome. > > i think a key bit to collaboration is going to be setting some ground > rules. > and the most important one imho is having a clear goal. > > off the top of my head, how about having the best plan 9 we can afford, > which runs on as much hardware, and as many vms as possible. right out > of the box. > > what do yall think? > > - erik > > --001a11c322468f5abb04f9ebe09f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
i like git. =C2=A0as it is a kind of archival file system,= one should be able to build a plan9 file system interface for it.

=


O= n Wed, May 21, 2014 at 9:25 AM, erik quanstrom <quanstro@quanstro.net<= /a>> wrote:
> I think such a beast wo= uld provide the foundations for a serious
> effort to bring the distributions back together. =C2=A0I know many res= ist
> such efforts because of Python (a pet hate of mine, even though I
> don't know it from Adam), HG and codereview and I resist accusing = them
> of reactionary behaviour; I do wish we could get past that problem, > though.

fwiw...

i use a derivative of nemo's patch system. =C2=A0all changes are applie= d through
patches. =C2=A0anyone can comment on a patch, and comments, and patch
dispositions are mailed to everyone on the list. =C2=A0the list is open to<= br> general discussion. =C2=A0the patch system allows folks to pull (not execut= ables)
or apply patches themselves, so in spirit it's closer to git than hg.
i'm open to any sort of gateway to hg/codereview/git that folks find us= eful.
i just don't want hg to be a requirement. =C2=A0one of the things i val= ue about
plan 9 is the fact that it's a self-contained system. =C2=A0requiring h= g and websites
runs counter this. =C2=A0i haven't carved out the time to do anything a= bout it,
but patches are welcome.

i think a key bit to collaboration is going to be setting some ground rules= .
and the most important one imho is having a clear goal.

off the top of my head, how about having the best plan 9 we can afford,
which runs on as much hardware, and as many vms as possible. =C2=A0right ou= t
of the box.

what do yall think?

- erik


--001a11c322468f5abb04f9ebe09f--