From: Harry Putnam <reader@newsguy.com>
Subject: Re: Downloading problems
Date: 01 Apr 1998 06:57:56 -0800 [thread overview]
Message-ID: <m3sonxio7f.fsf@org.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "01 Apr 1998 15:59:14 +0200"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Harry Putnam <reader@newsguy.com> writes:
>
> > Mine come up the other way around. With .el files showing newer than
> > byte compiled files and causes gnus to load the 'newer'.el files at
> > times.
>
> So the .el files have timestamps that are in the future?
Yes, At least in relation to my machine. This happened with a couple of
the later quassia releases. I only noticed it accidently by looking at
the messages buffer where there were messages saying gnus was loading .el
files because they were newer. Rather than get too involved figuring out
what was what, I just 'touched the .elc files and the messages went
away.
May have been related to having my machine time setup incorrectly.
Some time in the recent past I did do some tinkering with time
configurations. And as with all aspects of Linux, I didn't know what I
was doing very well, so botched it up several times. Not sure if this
might be related though.
Sorry I didn't check into it further. Once I discovered 'touching' .elc
files fixed it, I felt I was swamped enough with trying to learn all
this other new stuff. At any rate it hasn't happened again since about
quassia 35 or so.
--
Harry Putnam reader@newsguy.com
next prev parent reply other threads:[~1998-04-01 14:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-30 7:14 Mark Hovey
1998-03-30 11:36 ` Lars Balker Rasmussen
1998-03-30 22:44 ` Harry Putnam
1998-04-01 13:59 ` Lars Magne Ingebrigtsen
1998-04-01 14:57 ` Harry Putnam [this message]
1998-04-24 19:02 ` Lars Magne Ingebrigtsen
1998-04-24 19:09 ` Edward J. Sabol
1998-04-24 19:41 ` Lars Magne Ingebrigtsen
1998-04-01 13:58 ` Lars Magne Ingebrigtsen
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=m3sonxio7f.fsf@org.com \
--to=reader@newsguy.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 NNTP newsgroup(s).