From: Alexandre Oliva <oliva@lsd.ic.unicamp.br>
Cc: ding@gnus.org
Subject: Re: Feature request: decoding gnatsweb attachments
Date: 04 Nov 2000 19:15:21 -0200 [thread overview]
Message-ID: <ork8aj4exi.fsf@guarana.lsd.ic.unicamp.br> (raw)
In-Reply-To: ShengHuo ZHU's message of "04 Nov 2000 15:12:34 -0500"
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),
and widely used in projects such as GCC, glibc, GDB, GCJ, autoconf,
automake, libtool, and the list goes on :-)
> Is the attachment always at the end of the message?
I've never seen anything after it.
> Or Is there something marking the end of the attachment?
A blank line after the base64 encoded stream looks like a good bet.
I may send you a complete message, if you'd like to look into it.
For an example of Gnatsweb in action, see
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?database=gcc&user=guest&password=guest&cmd=login
The bug report containing the attachment I posted is bug #734.
Whenever someone posts a GCC bug report, it's forwarded to gcc-prs and
gcc-bugs@gcc.gnu.org, and attachments are encoded as in the snippet I
posted. The bug report in question, that I chose just because its
attachment was very small, is archived at
http://gcc.gnu.org/ml/gcc-prs/2000-q4/msg00213.html
--
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-04 21:15 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 [this message]
2000-11-04 22:46 ` Raja R Harinath
2000-11-06 3:35 ` Alexandre Oliva
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=ork8aj4exi.fsf@guarana.lsd.ic.unicamp.br \
--to=oliva@lsd.ic.unicamp.br \
--cc=ding@gnus.org \
/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).