feature request: patch file digests

feature request: patch file digests

[Greg Stark]

Hmm, There's this group I "read",  de.alt.sources.linux.patches, which posts
patches for new linux kernels.  Sort of handy for watching for when the
drivers I use actually change or new features get added.  But reading over
then thousand line patches that get posted in 7 parts is kinda awkward.

It would be cool if someone wrote a digest format for patch files.  
Each file could show up as a separate article making it easy to jump straight
to the file I want to see.  Hmm, thinking about this it might make more sense
to write a patch-mode.el and shar-mode.el and just have nndoc call them on the
article.  

I could try writing this, and probably will try. 
But I'm not sure I'll be able to do it

--
greg
Date: Sat, 6 Jan 96 23:01:46 -0500
From: Mail Delivery Subsystem <MAILER-DAEMON@MIT.EDU>
Subject: Returned mail: Unable to deliver mail
To: gsstark@MIT.EDU

   ----- Transcript of session follows -----
554 gsstark... Bad format for qf command: ding (ding

   ----- Unsent message follows -----
Received: by fierce-bad-rabbit.MIT.EDU (5.57/4.7) id AA11444; Sat, 6 Jan 96 23:01:46 -0500
Sender: gsstark@fierce-bad-rabbit.MIT.EDU
To: (ding) GNUS Mailing List <ding@ifi.uio.no>
Subject: feature request: handle broken From headers that include signature
From: gsstark@mit.edu (Greg Stark)
Date: 06 Jan 1996 23:01:42 -0500
In-Reply-To: craffert@sps.ml.com's message of Thu, 7 Dec 95 14:52:03 EST
Message-Id: <ycqlonkr6u1.fsf@fierce-bad-rabbit.MIT.EDU>
Organization: Massachvsetts Institvte of Technology
Lines: 19


There's a particular configuration error some people make that causes their
mailer to use their .signature file as their mail signature.  That is, use
their 5+ line signature in the From header of their mail messages.

Gnus doesn't simplify the header in any way when this happens, it does
something like this:

  +[  26: --------------------] Cockatrices, Basilisks and other Gargoyle Manufacturers

From: ------------------------------------------------------------------------------ <name-witheld@MIT.EDU>

Obviously the best it can do is some kind of heuristic, but it seems like Gnus
should be able to tell at least sometimes that it's not looking at the
author's name.  I would need to see a few more examples before I even had a
decent suggestion for what the heuristic should be.

--
greg