From: Latchesar Ionkov <lucho@ionkov.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9P libraries for Go
Date: Wed, 25 Nov 2009 09:18:28 -0700 [thread overview]
Message-ID: <f158dc670911250818i394eaf16jd85f23ef436003c4@mail.gmail.com> (raw)
In-Reply-To: <9ab217670911250805k59fd4ae2m87827feda62d28cb@mail.gmail.com>
I did four days ago. No comments yet. I am sure the go team is pretty
busy at the moment.
Lucho
On Wed, Nov 25, 2009 at 9:05 AM, Devon H. O'Dell <devon.odell@gmail.com> wrote:
> 2009/11/25 Latchesar Ionkov <lucho@ionkov.net>:
>> I added a Makefile in the repository that builds the packages outside
>> of the go tree.
>
> Any plans for filing a CL to add those to Go's src/pkg repo? I'm sure
> it would be welcomed.
>
> --dho
>
>> Thanks,
>> Lucho
>>
>> On Mon, Nov 23, 2009 at 7:04 PM, Roman Shaposhnik <roman@shaposhnik.org> wrote:
>>> On Sun, Nov 22, 2009 at 8:38 PM, Latchesar Ionkov <lucho@ionkov.net> wrote:
>>>> Hi,
>>>>
>>>> Andrey Mirtchovski and I wrote 9P server and client libraries/packages for Go.
>>>
>>> Perfect
>>>
>>>> The hg repository with the code is available at http://bitbucket.org/f2f/go9p/.
>>>>
>>>> Once downloaded the code should be moved to $GOROOT/src/pkg and
>>>> $GOROOT/src/pkg/Makefile should be modified so DIRS includes plan9/p,
>>>> plan9/p/clnt and plan9/p/srv directories. These directories should
>>>> also be added to the NOTEST variable.
>>>
>>> Could this be added to README, or better yet automated somehow?
>>>
>>> Thanks,
>>> Roman.
>>>
>>>
>>
>>
>
>
next prev parent reply other threads:[~2009-11-25 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 4:38 Latchesar Ionkov
2009-11-23 5:54 ` Bruce Ellis
2009-11-24 2:04 ` Roman Shaposhnik
2009-11-25 15:57 ` Latchesar Ionkov
2009-11-25 16:05 ` Devon H. O'Dell
2009-11-25 16:18 ` Latchesar Ionkov [this message]
2009-11-26 16:49 ` David Leimbach
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=f158dc670911250818i394eaf16jd85f23ef436003c4@mail.gmail.com \
--to=lucho@ionkov.net \
--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).