From: "John P. Harvey" <jpharvey@ptc.com>
To: "Rick Macdonald" <rickm@vsl.com>,
"Austin Bingham" <abingham@cadlips.ece.utexas.edu>
Cc: "GNATS Developement" <gnats-devel@sourceware.cygnus.com>
Subject: RE: gnatsweb attachments
Date: Fri, 03 Mar 2000 00:52:00 -0000 [thread overview]
Message-ID: <000a01bf84ed$874ed7b0$cc83fd84@john.gb.ptc.com> (raw)
In-Reply-To: <Pine.GSO.4.10.10003021210060.28147-100000@sys4>
I suspect they should be stored seperately if possible. We have
started using thius feature in gnatsweb and when get assigned a
new bug with attached files in the bug report it can tak a long
time to download the mail message. So i guess it doesnt matter
if the data is stored in the same file but the mail message
sent when a new bug is submitted probably shouldnt contain the attached
files.
Whilst talking about changes for 4.0 one request i've had is for the mail
message
sent from gnats for new bug reports to be similar to the gnatsweb mail which
is brief
but contains a hyperlink to the bug report instead of the whole bug report.
Since the
initial bug reports are sent by gnats and not gnatsweb i cant think of a way
to do this
at the moment.
Thanks
John
John Harvey
Tel: +44 (0)1454 453309
Fax: +44 (0)1454 626385
Email: jpharvey@ptc.com
> -----Original Message-----
> From: gnats-devel-owner@sourceware.cygnus.com
> [ mailto:gnats-devel-owner@sourceware.cygnus.com]On Behalf Of Rick
> Macdonald
> Sent: Thursday, March 02, 2000 7:15 PM
> To: Austin Bingham
> Cc: GNATS Developement
> Subject: Re: gnatsweb attachments
>
>
> On Thu, 2 Mar 2000, Austin Bingham wrote:
>
> > 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.
>
> Obviously, one shouldn't waste time doing this for gnats v3.x; it should
> be part of gnats v4.
>
> I just wanted to propose/discuss whether such attachments should be stored
> in separate files from the PR itself. Or, at least have view/edit options
> that don't pass the attachments back and forth. The point is that when
> browsing though PRs, you don't necessarily want huge attachments being
> sent to you when all you intend to do is change the responsible or close
> the PR, for example.
>
> ...RickM...
>
prev parent reply other threads:[~2000-03-03 0:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-02 9:36 Austin Bingham
2000-03-02 11:13 ` Rick Macdonald
2000-03-02 13:18 ` Austin Bingham
2000-03-03 0:52 ` John P. Harvey [this message]
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='000a01bf84ed$874ed7b0$cc83fd84@john.gb.ptc.com' \
--to=jpharvey@ptc.com \
--cc=abingham@cadlips.ece.utexas.edu \
--cc=gnats-devel@sourceware.cygnus.com \
--cc=rickm@vsl.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).