From: Joe Buck <jbuck@synopsys.com>
To: bothner@cygnus.com (Per Bothner)
Cc: rth@cygnus.com, egcs@cygnus.com
Subject: Re: viewing <> constructs via the web archive
Date: Sun, 19 Apr 1998 18:10:00 -0000 [thread overview]
Message-ID: <199804192230.PAA16535@atrus.synopsys.com> (raw)
In-Reply-To: <199804181608.JAA28486@cygnus.com>
Per writes:
> I am not saying we should mung patches sent to the list; I am saying
> that you have to mung text when you convert it to html to be stored
> in a mail archive. Not doing the munging *loses* information,
> because you can no longer tell html directives from text.
>
> If the goal is that you want to be able to use an html file as
> direct input to patch, well I am sorry, that is just plain bogus.
> You can't do that. Use the original un-html'd mail message,
> which is still available in the base (non-hypermail) archive.
If disk space is not a problem, one possibility is to save each message
twice, as .txt and .html; munge the .html version as hypermail usually
does (with respect to <, >, & etc), and have the .html version link to
the .txt version. Alternatively, the .txt version could be saved only
if there is a patch present (the patch program has code to detect this;
I don't know if patch can be used just as a patch-detector rather than
a patch-applier.
next prev parent reply other threads:[~1998-04-19 18:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-17 14:49 Daniel Karipides
1998-04-17 22:05 ` Per Bothner
1998-04-18 1:43 ` Richard Henderson
1998-04-18 9:08 ` Per Bothner
1998-04-19 18:10 ` Joe Buck [this message]
1998-04-25 17:40 ` Gerald Pfeifer
1998-04-25 21:42 ` Jeffrey A Law
1998-04-18 8:18 Daniel Egger
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=199804192230.PAA16535@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=bothner@cygnus.com \
--cc=egcs@cygnus.com \
--cc=rth@cygnus.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).