From: "Austin Bingham" <abingham@lips.utexas.edu>
To: "GNATS Developement" <gnats-devel@sourceware.cygnus.com>
Subject: gnatsweb attachments
Date: Thu, 02 Mar 2000 09:36:00 -0000 [thread overview]
Message-ID: <03df01bf846d$c89bf930$60c45380@amphibolips> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]
I noticed that there was some discussion of
gnatsweb attachments a while back. Some of our gnats users have expressed a
desire to have gnatsweb attachments treated as regular mail attachments when
they are notified of PR creation, etc., and I think this is a very reasonable
request.
Â
It looks like gnats web makes a good effort to make
it's attachments MIME-compliant, but the rest of the mail info is not written to
allow the files to be treated as full mail attachments. I could be way off base,
but based on how other mails seem to indicate their attachments, I think that's
accurate. Basically, it looks like the notification mail has to claim to be a
multi-part mime file with a part-boundary defined.
Â
One way to approach this issue, which was forwarded
by someone earlier, is to have an official recognition of file attachments
in the GNATS core. This would be nice, but it would require some time and effort
on someone's part. Are there any other ideas? I think this would be a very handy
extension to current GNATS functionality.
Â
Austin Bingham Laboratory for Intelligent
Processes and Systems University of Texas at Austin abingham@mail.utexas.edu
next reply other threads:[~2000-03-02 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-02 9:36 Austin Bingham [this message]
2000-03-02 11:13 ` Rick Macdonald
2000-03-02 13:18 ` Austin Bingham
2000-03-03 0:52 ` John P. Harvey
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='03df01bf846d$c89bf930$60c45380@amphibolips' \
--to=abingham@lips.utexas.edu \
--cc=gnats-devel@sourceware.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).