From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Replica (partly?) stuck in time
Date: Thu, 20 May 2010 15:46:21 +0000 [thread overview]
Message-ID: <AANLkTimUBVfSWccjcK1gBXEI_oA5UAPPjkK-7hhIqKJw@mail.gmail.com> (raw)
In-Reply-To: <AANLkTilXkeBLKI_PI5IYBXT8UGvHJKDKddV-CKSkRTJc@mail.gmail.com>
On Thu, May 20, 2010 at 3:23 PM, David Leimbach <leimy2k@gmail.com> wrote:
> Who's updating the bitbucket.org sources, and how does one get started doing
> that?
me.
I try to do it daily. There's still a few glitches (e.g. python on
plan 9 still has a way of exploding at times ... and 9vx can explode
too ...) so I have to do it by hand; I want it to be a cron job.
ron
next prev parent reply other threads:[~2010-05-20 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 5:08 a
2010-05-20 5:45 ` ron minnich
2010-05-20 15:23 ` David Leimbach
2010-05-20 15:24 ` David Leimbach
2010-05-20 15:46 ` ron minnich [this message]
2010-05-20 15:48 ` erik quanstrom
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=AANLkTimUBVfSWccjcK1gBXEI_oA5UAPPjkK-7hhIqKJw@mail.gmail.com \
--to=rminnich@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).