From: Alexandre Oliva <oliva@lsd.ic.unicamp.br>
Cc: ShengHuo ZHU <zsh@cs.rochester.edu>, ding@gnus.org
Subject: Re: Feature request: decoding gnatsweb attachments
Date: 06 Nov 2000 01:35:20 -0200 [thread overview]
Message-ID: <or4s1l3h8n.fsf@guarana.lsd.ic.unicamp.br> (raw)
In-Reply-To: Raja R Harinath's message of "04 Nov 2000 16:46:10 -0600"
On Nov 4, 2000, Raja R Harinath <harinath@cs.umn.edu> wrote:
> Alexandre Oliva <oliva@lsd.ic.unicamp.br> writes:
>> On Nov 4, 2000, ShengHuo ZHU <zsh@cs.rochester.edu> wrote:
>> > I never received anything like this. Where does it come from?
>>
>> A bug tracking system called Gnats. It's Free Software (of course),
> [snip]
> Then you should be able to fix it to send MIME attachments instead ;-)
Good point :-)
> Isn't that a more generally useful fix rather than looking for a
> gnus-specific solution?
Except that I'd have to ask the maintainers of Gnats in all projects I
run to install the patch. And I know some of them aren't exactly fans
of MIME :-)
Besides, this wouldn't help me deal with the hundreds of messages I
keep in local folders for fast access :-)
I just thought it would be easier to do in Gnus, since it's already
got all the magic needed to cope with base64 encoding, and already has
special-cases for uuencoded parts.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
next prev parent reply other threads:[~2000-11-06 3:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-04 7:24 Alexandre Oliva
2000-11-04 20:12 ` ShengHuo ZHU
2000-11-04 21:15 ` Alexandre Oliva
2000-11-04 22:46 ` Raja R Harinath
2000-11-06 3:35 ` Alexandre Oliva [this message]
2000-11-05 0:17 ` ShengHuo ZHU
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=or4s1l3h8n.fsf@guarana.lsd.ic.unicamp.br \
--to=oliva@lsd.ic.unicamp.br \
--cc=ding@gnus.org \
--cc=zsh@cs.rochester.edu \
/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).