9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Darren Bane <darren.bane@gmail.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Re: let's talk contrib
Date: Sun, 29 Apr 2007 03:37:43 +0100	[thread overview]
Message-ID: <f110dn$s9d$1@majestic.ukshells.co.uk> (raw)
In-Reply-To: <32d987d50704281907v1a76412eo68b5716cc1a3c55b@mail.gmail.com>

Federico Benavento <benavento@gmail.com> wrote:
> hola,
> 
> I guess we need some conventions, for example where are we
> going to put all the contrib files in our trees?
> If we had such convention we could just use replica.

This came up on the Inferno list some time ago.

  http://article.gmane.org/gmane.os.inferno.general/2629

I'm not sure, but are the Plan 9 equivalents /src, /include and
/bin?

!snipped!
-- 
Darren Bane



  reply	other threads:[~2007-04-29  2:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-28 18:03 [9fans] " mattmobile
2007-04-28 18:10 ` Lucio De Re
2007-04-29  1:11   ` erik quanstrom
2007-04-29  2:07     ` Federico Benavento
2007-04-29  2:37       ` Darren Bane [this message]
2007-04-29 20:10       ` Russ Cox

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='f110dn$s9d$1@majestic.ukshells.co.uk' \
    --to=darren.bane@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).