I agree with Brian that micro-bugs should probably be reported to the
maintainer, just because it takes more work to contact the reporter and
close the bug than to fix it. However, in this case the reporter has to
keep his _own_ bug tracking system, if he wants to make sure that the
maintainer
On Sat, 24 Aug 1996, Ian Jackson wrote:
> This is a different matter. Encouraging people to discuss things that
> might or might not be bugs is fine.
>
> Discouraging people from reporting things that definitely are bugs is
> not fine.
>
I agree completely, but I will still contend that the app
Dale Scheetz writes ("Re: Bug#4164: Ferret extended description has blank lines
"):
...
> Objections to reporting something as a bug are not founded on this
> concept. No one feels personaly "put down" by a bug report. Those of us
> who object to "trivial" b
On Fri, 16 Aug 1996, Lars Wirzenius wrote:
> "Brian C. White":
> > By the way, for such tiny things, it's usually considered better
> > to just notify the maintainer instead of adding the overhead of
> > a full bug report.
>
> I disagree.
We seem to be divided fairly evenly on this issue.
>
"Brian C. White":
> By the way, for such tiny things, it's usually considered better
> to just notify the maintainer instead of adding the overhead of
> a full bug report.
I disagree. The bug list is not a shame pole! It's a trivial way for
users to reach maintainers -- there's only one address
5 matches
Mail list logo
