From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: ucs-tables.el contains unbalanced parenthesis...
Date: Tue, 26 Mar 2002 13:29:04 +0100 [thread overview]
Message-ID: <vafvgbj7bsf.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <87d6xrwpi1.fsf@inanna.rimspace.net> (Daniel Pittman's message of "Tue, 26 Mar 2002 22:13:42 +1100")
Daniel Pittman <daniel@rimspace.net> writes:
> Anyway, I can work around the problem without too much hassle -- it's
> not like I can't live without building autoloads there when things
> update.
Hm. Maybe the stuff in contrib shouldn't be used unconditionally.
It should only be used when really needed. At least I gather that's
the idea of the contrib directory.
kai
--
Silence is foo!
next prev parent reply other threads:[~2002-03-26 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-26 6:21 Daniel Pittman
2002-03-26 10:21 ` Kai Großjohann
2002-03-26 11:13 ` Daniel Pittman
2002-03-26 12:29 ` Kai Großjohann [this message]
2002-03-26 13:05 ` Daniel Pittman
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=vafvgbj7bsf.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.org \
/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).