From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: lpath (was: Re: Cup design (competition))
Date: 30 Sep 1997 22:02:46 +0200 [thread overview]
Message-ID: <rjsoumzi1l.fsf_-_@zuse.dina.kvl.dk> (raw)
In-Reply-To: Lars Balker Rasmussen's message of "30 Sep 1997 21:34:48 +0200"
Lars Balker Rasmussen <lbr@mjolner.dk> writes:
> rename custom's lpath.el to lpath.el.tmp
> unpack and compile qgnus 0.11
> rename custom's lpath.el.tmp to lpath.el
Custom doesn't need lpath except for compiling itself, so the last
step is unnecessary. I don't see any reason why qgnus should need
lpath at all, it looks to me like it is a relic from the distant age
where custom was bundled with gnus.
next prev parent reply other threads:[~1997-09-30 20:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-30 8:12 Cup design (competition) Lars Magne Ingebrigtsen
1997-09-30 9:45 ` Andy Eskilsson
1997-09-30 17:51 ` Danny Siu
1997-09-30 18:27 ` Lars Balker Rasmussen
1997-09-30 19:17 ` Lars Magne Ingebrigtsen
1997-09-30 18:29 ` Colin Rafferty
1997-09-30 16:25 ` Stefan Waldherr
1997-09-30 18:01 ` Justin Sheehy
1997-09-30 19:34 ` Lars Balker Rasmussen
1997-09-30 20:02 ` Per Abrahamsen [this message]
1997-09-30 20:45 ` Karl Kleinpaste
1997-09-30 21:42 ` Hrvoje Niksic
1997-10-03 22:01 ` Lars Magne Ingebrigtsen
1997-10-03 22:02 ` 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=rjsoumzi1l.fsf_-_@zuse.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
/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).