9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Roman V. Shaposhnik" <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] plan9port lacks exportfs server
Date: Wed, 22 Oct 2008 22:26:54 -0700	[thread overview]
Message-ID: <1224739614.11627.124.camel@goose.sun.com> (raw)
In-Reply-To: <dd6fe68a0810181020n4136964cr17c2f8aa05839573@mail.gmail.com>

On Sat, 2008-10-18 at 10:20 -0700, Russ Cox wrote:
> > Hence the question -- would you be in favor
> > of continue adding things as needed. And
> > if so, what kind of of groundwork would
> > you expect from the contributors?
>
> Usually it is as simple as adding it to your own tree,
> adapting the mkfile, and making it build.

Absolutely! And for the internal project I'm already
doing exactly that for nfsserver. My question had
more to do with the usability issues, rather than
engineering. It seems that useful bits that didn't
get into plan9port right away tend to be scattered
throughout "other trees" instead of being available
at a canonical location. 9pcon comes readily to
mind, but I'm sure there are others. Personally, I've
only stumbled on a need to fetch 9pcon so far plus
my own changes, but even that can be described as
a mild inconvenience.

Thus, I was thinking that perhaps if you could
lay the ground rules for how new things could
be added to your canonical plan9port tree these
little annoyances could be dealt with.

Thanks,
Roman.




  reply	other threads:[~2008-10-23  5:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-04 22:15 Roman Shaposhnik
2008-10-06 16:24 ` Russ Cox
2008-10-07  0:36   ` sqweek
2008-10-07  3:43   ` Roman V. Shaposhnik
2008-10-18 17:20     ` Russ Cox
2008-10-23  5:26       ` Roman V. Shaposhnik [this message]
2008-10-23 17:39         ` Russ Cox
2008-10-30 18:07           ` Enrico Weigelt
2008-10-30 21:15             ` Roman V. Shaposhnik
2008-11-01 19:05               ` Enrico Weigelt
2008-11-01 20:40                 ` Roman Shaposhnik
2008-11-03  0:15                   ` Enrico Weigelt
2008-11-04  1:23                     ` Roman V. Shaposhnik
2008-11-04  1:23                     ` Roman V. Shaposhnik

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=1224739614.11627.124.camel@goose.sun.com \
    --to=rvs@sun.com \
    --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).