From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Elijah Meeks <elijahmeeks@yahoo.com>
Cc: xconq7@sources.redhat.com
Subject: Re: Rebuilding Units That Turn
Date: Thu, 20 Nov 2003 00:01:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0311191831300.31399-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <20031119231348.89073.qmail@web13108.mail.yahoo.com>
On Wed, 19 Nov 2003, Elijah Meeks wrote:
> builds it, leaving you with just one unit. How's
> upgrade work and is it easy to implement/use?
If you are talking about the time.g upgrade mechanism, the answer
is that I don't know; I have not bothered to look yet. IIRC,
Lincoln knows something about it, so I'll defer the real answer to
him or another knowledgable person. You could also look in
time.g (I think that is the file) and see if you can find it and
figure it out.
Eric
next prev parent reply other threads:[~2003-11-19 23:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 22:41 Elijah Meeks
2003-11-19 22:44 ` Eric McDonald
2003-11-19 23:37 ` Elijah Meeks
2003-11-20 0:01 ` Eric McDonald [this message]
2003-11-20 0:13 ` Lincoln Peters
2003-11-20 18:00 ` Jim Kingdon
2003-11-20 18:52 ` Eric McDonald
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=Pine.LNX.4.44.0311191831300.31399-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=elijahmeeks@yahoo.com \
--cc=xconq7@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).