9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] going too far?
Date: Tue, 19 Feb 2013 01:39:46 +0000	[thread overview]
Message-ID: <CAOw7k5gyp4voPB6LR3KOEYNtv-XMx1S80E-xS0DaZ37bEFGmqQ@mail.gmail.com> (raw)
In-Reply-To: <CAOw7k5hdBVsEALrg-O_XKVynrG2vncvMxwF1u=yDi0hzfh1F-g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 377 bytes --]

On 19 February 2013 01:36, Charles Forsyth <charles.forsyth@gmail.com>wrote:

> I wonder if there's something about nemo's example
> that gets {go clean ...} wandering through all the src/cmd stuff so often.
>

One difference is that I had floren's code outside the go tree, although it
would still need to
enter that to gather the package dependencies for ellipsoid.

[-- Attachment #2: Type: text/html, Size: 729 bytes --]

  reply	other threads:[~2013-02-19  1:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18 18:15 Francisco J Ballesteros
2013-02-18 18:41 ` John Floren
2013-02-18 19:22   ` andrey mirtchovski
2013-02-18 19:23     ` andrey mirtchovski
2013-02-19  1:36       ` Charles Forsyth
2013-02-19  1:39         ` Charles Forsyth [this message]
2013-02-19  1:57           ` andrey mirtchovski
2013-02-19  2:27             ` erik quanstrom
2013-02-19  4:14               ` erik quanstrom
2013-02-19  3:07         ` andrey mirtchovski
2013-02-19  9:32       ` Charles Forsyth
2013-02-19 10:05         ` Bruce Ellis
2013-02-19 10:33           ` Charles Forsyth
2013-02-19 11:57             ` lucio
2013-02-19 23:33               ` Anthony Martin
2013-02-20  8:06                 ` [9fans] Go tool capabilities (Was: going too far?) lucio
2013-02-20  8:06                 ` lucio
2013-02-19  2:29     ` [9fans] going too far? erik quanstrom
2013-02-19  3:08       ` andrey mirtchovski
2013-02-19  3:22         ` erik quanstrom
2013-02-20 11:45 ` Anthony Martin

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=CAOw7k5gyp4voPB6LR3KOEYNtv-XMx1S80E-xS0DaZ37bEFGmqQ@mail.gmail.com \
    --to=charles.forsyth@gmail.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).