From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Fix to the copyright.el regexp to catch multi-line copyrights.
Date: Tue, 01 Jan 2002 03:23:53 +0100 [thread overview]
Message-ID: <m3vgem3j2e.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m3zo3y3j9m.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> MIME-Version: 1.0
> Content-Type: text/plain; charset=utf-8
> Content-Transfer-Encoding: quoted-printable
[...]
> \\|[Cc]opyright\\s *:?\\s *[\251=C2=81=C2=A9]\\)\
Uhm -- what happened here? The MIME headers ended up in the body of
the message. Weird.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2002-01-01 2:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-01 2:19 Lars Magne Ingebrigtsen
2002-01-01 2:23 ` Lars Magne Ingebrigtsen [this message]
2002-01-03 21:21 ` Daniel Pfeiffer
2002-01-04 4:45 ` 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=m3vgem3j2e.fsf@quimbies.gnus.org \
--to=larsi@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).