From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: hack of .overview files
Date: 03 Mar 1998 18:37:43 +0100 [thread overview]
Message-ID: <rjsoozk74o.fsf@zuse.+dina.kvl.dk> (raw)
In-Reply-To: <uttbtvnkbof.fsf@gs236.sp.cs.cmu.edu>
Mark Moll <mmoll@cs.cmu.edu> writes:
> (I know the "from" header should only be checked once, but I am a total
> elisp illiterate.) Is there any reason why this is a bad idea? If not, is it
> worth making this behavior an option?
There is a standard format for `.overview'. The format is extensible,
so you _could_ add the "To: " header.
I'd feel bad about adding an (even optional) kludge that breaks a
standard file format, especially when the file format is flexible
enough to add the extra information without breaking it.
next prev parent reply other threads:[~1998-03-03 17:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-03 15:59 Mark Moll
1998-03-03 16:04 ` Stefan Waldherr
1998-03-03 16:42 ` Wes Hardaker
1998-03-03 17:37 ` Per Abrahamsen [this message]
1998-03-03 19:55 ` hack of .overview files [take 2] Mark Moll
1998-03-04 11:16 ` Per Abrahamsen
1998-03-05 11:20 ` threading emails (Was: hack of .overview...) Steinar Bang
1998-03-05 13:07 ` Per Abrahamsen
1998-03-07 12:59 ` hack of .overview files [take 2] 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=rjsoozk74o.fsf@zuse.+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).