From: Ryan Gonzalez <rymg19@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] ken cc for linux
Date: Fri, 13 Mar 2015 12:59:51 -0500 [thread overview]
Message-ID: <CAO41-mMTjZop9dquTdjAys3oKtMQ37i-EJVQmfmCfyjm0LpThQ@mail.gmail.com> (raw)
In-Reply-To: <CAOw7k5iemO9fQpjSMh0rFEHsMr0S2xyni5sNbeRLSn2gzfYfVw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
I prefer GitHub. Much nicer, easier to use, has a PR system (no patches!),
etc.
The website also works better on mobile devices. Google Code's source
browser doesn't work on my phone.
I wouldn't say it suddenly vanished, though. A quick search shows some were
predicting this would happen. Lots of major projects have moved to GitHub
or Bitbucket.
On Fri, Mar 13, 2015 at 8:24 AM, Charles Forsyth <charles.forsyth@gmail.com>
wrote:
>
> On 13 March 2015 at 01:31, erik quanstrom <quanstro@quanstro.net> wrote:
>
>> was, as in google code is dead.
>
>
> It's a good example of how the cloudy future is seriously unsettled by
> services suddenly vanishing,
> even from big suppliers. Also, I rather trust the Google storage
> infrastructure, but I'm not sure about the other two.
>
--
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/
[-- Attachment #2: Type: text/html, Size: 1958 bytes --]
next prev parent reply other threads:[~2015-03-13 17:59 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 20:30 Aharon Robbins
2015-03-11 20:34 ` Aram Hăvărneanu
2015-03-11 21:04 ` Ryan Gonzalez
2015-03-11 21:54 ` Quintile
2015-03-11 23:04 ` Ryan Gonzalez
2015-03-11 23:19 ` Steve Simon
2015-03-12 6:39 ` arnold
2015-03-13 1:31 ` erik quanstrom
2015-03-13 13:24 ` Charles Forsyth
2015-03-13 17:59 ` Ryan Gonzalez [this message]
2015-03-13 18:19 ` Kurt H Maier
2015-03-19 15:35 ` Jeff Sickel
2015-03-19 16:09 ` [9fans] using git arnold
2015-03-19 16:22 ` Stanley Lieber
2015-03-19 16:34 ` Charles Forsyth
2015-03-19 16:36 ` Charles Forsyth
2015-03-19 16:39 ` Federico Benavento
2015-04-03 18:46 ` Jeff Sickel
2015-03-19 18:03 ` Skip Tavakkolian
2015-03-19 20:30 ` Jeff Sickel
2015-03-19 21:46 ` Skip Tavakkolian
2015-03-19 21:54 ` Devon H. O'Dell
2015-03-20 1:02 ` Kurt H Maier
2015-03-19 18:26 ` arnold
2015-03-28 11:14 ` Charles Forsyth
2015-03-28 14:00 ` Paul Lalonde
2015-03-30 9:48 ` Giacomo Tesio
2015-03-30 9:55 ` Giacomo Tesio
2015-03-30 16:16 ` Jeff Sickel
2015-03-30 19:47 ` Stanley Lieber
2015-03-30 20:41 ` Bakul Shah
2015-03-30 20:20 ` Giacomo Tesio
2015-03-30 20:32 ` Ryan Gonzalez
2015-03-31 3:17 ` arnold
2015-03-19 17:00 ` Jeff Sickel
2015-03-19 17:36 ` Ori Bernstein
2015-03-12 8:50 ` [9fans] ken cc for linux Aram Hăvărneanu
2015-03-12 17:53 ` Ryan Gonzalez
2015-03-12 8:51 ` Aram Hăvărneanu
2015-03-12 10:06 ` Charles Forsyth
2015-03-12 15:23 ` Charles Forsyth
2015-03-12 15:41 ` Brantley Coile
2015-03-12 17:14 ` Charles Forsyth
2015-03-13 1:28 ` erik quanstrom
2015-03-12 17:52 ` Ryan Gonzalez
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=CAO41-mMTjZop9dquTdjAys3oKtMQ37i-EJVQmfmCfyjm0LpThQ@mail.gmail.com \
--to=rymg19@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).