9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Jens Staal <staal1978@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] 9front-issues@9front.org is now bugs@9front.org
Date: Fri, 13 Mar 2015 05:54:17 +0100	[thread overview]
Message-ID: <CAK8RtFqVf4hF5fnPoEmTVJomv4hzHMHj1qLrK3czRAbryiqgbw@mail.gmail.com> (raw)
In-Reply-To: <c2e946c6f7698c0d975593f947e7e2cb.squirrel@box718.bluehost.com>

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

I will miss my ports2plan9 :(

Real life (kids and work) has made it hard to play with porting so this
project will die.

I think all binaries (and modified source bundled in the pkgs) are
available under /n/sources/contrib/staal1978

I will check if something is missing and upload it there if that is the
case.
 Den 13 mar 2015 01:38 skrev <tony@instaview.com>:

> yikes.. a sad day for a lot of projects...
>
> > Google Code is shutting down.
> >
> > Previously, the 9front Google Code issue tracker sent e-mail
> > notifications to 9front-issues@9front.org.
> >
> > Effective immediately, I have copied the 9front-issues@9front.org
> > subscriber list to bugs@9front.org. From now on, post information
> > about bugs to this list by sending mail to bugs@9front.org. The
> > Google Code issue tracker will no longer be used.
> >
> > To unsubscribe, send a message with a body containing only the
> > word unsubscribe to bugs-owner@9front.org.
> >
> > Information about the future of 9front project hosting will be
> > forthcoming.
> >
> > http://massivefictions.com/ACTRON/v4/003/png/04.png
> >
> > sl
> >
>
>
>

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

      reply	other threads:[~2015-03-13  4:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13  0:00 sl
2015-03-13  0:37 ` [9front] " tony
2015-03-13  4:54   ` Jens Staal [this message]

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=CAK8RtFqVf4hF5fnPoEmTVJomv4hzHMHj1qLrK3czRAbryiqgbw@mail.gmail.com \
    --to=staal1978@gmail.com \
    --cc=9front@9front.org \
    /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).