From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: integrating x-face stuff
Date: 12 Jan 2001 12:52:32 +0100 [thread overview]
Message-ID: <rj8zoh3s3j.fsf@ssv2.dina.kvl.dk> (raw)
In-Reply-To: <rjd7dt3s68.fsf@ssv2.dina.kvl.dk>
Per Abrahamsen <abraham@dina.kvl.dk> writes:
> kristian ragndahl <ragndahl@postmaster.co.uk> writes:
>
> > However, it might not work since the header can contain
> > inappropriate characters ("'() etc).
>
> Only " would be a problem in a cut&paste.
I'm wrong, even " would *not* be a problem in a cut&paste, since
customize will quote it as needed.
prev parent reply other threads:[~2001-01-12 11:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-11 4:08 Nick Papadonis
2001-01-11 9:52 ` Per Abrahamsen
2001-01-11 10:02 ` Nick Papadonis
2001-01-11 11:28 ` Per Abrahamsen
2001-01-11 22:30 ` Nick Papadonis
2001-01-12 21:52 ` Kai Großjohann
2001-01-12 22:00 ` Kai Großjohann
2001-01-12 22:46 ` Nick Papadonis
2001-01-12 22:53 ` Charles Sebold
2001-01-12 23:13 ` Jack Twilley
2001-01-12 23:31 ` Kai Großjohann
2001-01-13 12:29 ` Nick Papadonis
[not found] ` <86ae8x5zf1.fsf@blowfish.brfmasthugget.se>
2001-01-12 11:50 ` Per Abrahamsen
2001-01-12 11:52 ` Per Abrahamsen [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=rj8zoh3s3j.fsf@ssv2.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).