From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Compile Problem...
Date: Fri, 23 Jan 2004 16:41:28 -0500 [thread overview]
Message-ID: <aeb1d767066be56981cd8569e64e600f@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0401231430480.12084-100000@einstein.ssz.com>
[-- Attachment #1: Type: text/plain, Size: 75 bytes --]
Sure, it scans once every half hour on the half hour to see what's changed.
[-- Attachment #2: Type: message/rfc822, Size: 2867 bytes --]
From: Jim Choate <ravage@einstein.ssz.com>
To: <9fans@cse.psu.edu>
Cc: <hangar18-general@open-forge.com>
Subject: Re: [9fans] Compile Problem...
Date: Fri, 23 Jan 2004 14:34:19 -0600 (CST)
Message-ID: <Pine.LNX.4.33.0401231430480.12084-100000@einstein.ssz.com>
David & Andrey,
Thanks for the help.
On Fri, 23 Jan 2004, David Presotto wrote:
> Or better still, wait for the next scan and just pull. SOme stuff
> rode in with an update we did yesterday.
I have zero problem giving it some time and doing another pull. Would
tomorrow (Sat.) be soon enough for the scan to take effect and move the
new source out to the repository? I'm heading out of the office as soon as
I send this ;) I'll check email later tonight.
-- --
Open Forge, LLC 24/365 Onsite Support for PCs, Networks, & Game Consoles
512-695-4126 (Austin, Tx.) help@open-forge.com irc.open-forge.com
Hangar 18 Open Source Distributed Computing Using Plan 9 & Linux
512-451-7087 http://open-forge.org/hangar18 irc.open-forge.org
James Choate 512-451-7087 ravage@ssz.com jchoate@open-forge.com
prev parent reply other threads:[~2004-01-23 21:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 16:43 Jim Choate
2004-01-23 16:50 ` mirtchov
2004-01-23 18:12 ` Jim Choate
2004-01-23 18:34 ` mirtchov
2004-01-23 18:41 ` David Presotto
2004-01-23 20:34 ` Jim Choate
2004-01-23 21:41 ` David Presotto [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=aeb1d767066be56981cd8569e64e600f@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--cc=9fans@cse.psu.edu \
/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).