From: Tom Gall <gall@rochcivictheatre.org>
To: Takashi Oe <toe@unlserve.unl.edu>, linuxppc-dev@lists.linuxppc.org
Subject: Re: about automated emails from ppclinux@sourceforge.net
Date: Sat, 10 Feb 2001 15:24:46 -0600 [thread overview]
Message-ID: <3A85B19E.2EACA3F7@rochcivictheatre.org> (raw)
In-Reply-To: Pine.A41.3.96LJ1.1b7.1010210142304.77892A-100000@unlserve.unl.edu
Takashi Oe wrote:
>
> Hi,
>
> I was wondering if you or somebody responsible for the sourceforge site
> could reconsider about how "bug" reports and whatnot are fed to
> linuxppc-dev mailing list.
Hi Takashi,
If you are on the dev list I would hope you are interested in bug
reports. This forwarding has been in place since last year so folks
could keep in tune with the SourceForge site.
> I would much rather prefer if the person who actually submitted the bug
> report to (or changed the status at) the sourceforge site would CC this
> list in person.
I disagree. Newbies don't necessary know about the linuxppc-dev list
much less the commit list much less where folks hang out in IRC etc etc.
People who take the time to test and post bug reports are valueable!
Sure not every bug is a real problem but that's the life of a developer.
> The autofeed does not show how we may possibly inquire further on the
> report itself. For example, the last report about parted requiring reboot
> or something seemed like more of a generic Linux issue or just that the
> app is broken, and I may perhaps want to ask for details. Then, who
> should I send the question to? [Ok, I can find your email address and
> others' if I work at it, but that's not my point.]
At the VERY bottom of the bug report is a link that you can click on
to get more information about the bug. From there you can get the sf id
of the people involved in the bugs report and fix. Recall that
sourceforge user ids are email addresses.
so userid@users.sourceforge.net as an example.
> If anything, is it possible to stop the autofeed now and instead to
> encourage whoever uses the site to CC their words to linuxppc-dev?
Sourceforge doesn't have that feature. You can't cc a bug report
somewhere. But that's not to say that those kinds of options couldn't be
added. I know some of the VA Linux guys... sounds like a good
suggestion.
At the moment I am against stopping the auto feed as then folks who
are not monitoring the sourceforge site miss out on both new bugs as
well as fixes to current bugs.
Completely cutting off the flow of information to me isn't the answer.
--
Regards,
Tom
--------------------------------------------------------------
Linux Guy "My heart is human, my blood is boiling,
gall@rochcivictheatre.org my brain IBM" -- Mr Roboto, Styxx
tom_gall@vnet.ibm.com
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-10 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E14RgRv-0007bq-00@usw-sf-web3.sourceforge.net>
2001-02-10 20:47 ` about automated emails from ppclinux@sourceforge.net Takashi Oe
2001-02-10 21:15 ` Hollis R Blanchard
2001-02-10 21:24 ` Tom Gall [this message]
2001-02-10 22:20 ` Takashi Oe
2001-02-11 16:33 ` Michael Schmitz
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=3A85B19E.2EACA3F7@rochcivictheatre.org \
--to=gall@rochcivictheatre.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=toe@unlserve.unl.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).