From: sigurd@12move.de (Karl Pflästerer)
Subject: Re: Problems with new space character syntax change?
Date: Sat, 15 Feb 2003 00:03:11 +0100 [thread overview]
Message-ID: <m38ywi1n8i.fsf@hamster.pflaesterer.de> (raw)
In-Reply-To: <84znoy60w2.fsf@lucy.is.informatik.uni-duisburg.de>
Kai Großjohann <- kai.grossjohann@uni-duisburg.de wrote:
> Is anyone else seeing problems building Gnus with the most recent
> CVS? I *think* it's sufficient to frob a couple of places that look
> like (? 42) to look like (? 42), but I'm not sure.
I see no problems here (did an update 10 minutes ago).
bye
KP
--
"But it has nothing to do with what a _value_ is. This has to do with
whether you pass whatever-a-value-is or wherever-whatever-is-a-value-is
whenever you pass an argument to a function. (Call it the Shakira
theory. :)" [Erik Naggum in cll über call-by-value und call-by-reference]
prev parent reply other threads:[~2003-02-14 23:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 20:52 Kai Großjohann
2003-02-14 23:03 ` Karl Pflästerer [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=m38ywi1n8i.fsf@hamster.pflaesterer.de \
--to=sigurd@12move.de \
/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).