> > The following bug reports *must* be fixed before the current frozen Debian
> > distribution can progress further in its development cycle. Reminders have
> > been sent to the maintainers of these packages yet nothing has been done to
> ^
Previously Branden Robinson wrote:
> Please watch your generalizations. I am working on all of these and in
> fact made a test build of 3.3.2.2-1 yesterday. It upsets me when the
> implication is made that I am sitting on my hands.
me too
A lot of those are really being worked upon. Several fix
On Mon, Jun 15, 1998 at 09:19:30AM -0400, Brian White wrote:
> The following bug reports *must* be fixed before the current frozen Debian
> distribution can progress further in its development cycle. Reminders have
> been sent to the maintainers of these packages yet nothing has been done to
> > The message is intended to inform _others_ of the problems that exists
> > in order to encourage them to help solve those problems. When people
> > whine about "When is Hamm going to be released?" I can just point them
> > to this weekly message and ask them what they've done to help.
>
> So t
On Thu, 7 May 1998, Brian White wrote:
> The message is intended to inform _others_ of the problems that exists
> in order to encourage them to help solve those problems. When people
> whine about "When is Hamm going to be released?" I can just point them
> to this weekly message and ask them wha
> > > > Several people have asked for this, but maintainers already get separate
> > > > reports about their packages and reports by package are available on
> > > > the web site, so I don't really understand the usefulness of presenting
> > > > it that way here. Is there something I'm missing?
>
On Wed, 6 May 1998, Brian White wrote:
> > > Several people have asked for this, but maintainers already get separate
> > > reports about their packages and reports by package are available on
> > > the web site, so I don't really understand the usefulness of presenting
> > > it that way here. Is
On Fri, May 01, 1998 at 12:38:24PM -0400, Brian White wrote:
> > Brian, this is a useful list, but please sort it by Maintainer or by Package
> > rather than by bug number:
>
> Several people have asked for this, but maintainers already get separate
> reports about their packages and reports by pa
On Fri, 1 May 1998, Brian White wrote:
> > Brian, this is a useful list, but please sort it by Maintainer or by Package
> > rather than by bug number:
>
> Several people have asked for this, but maintainers already get separate
> reports about their packages and reports by package are available o
Brian White wrote:
>> Brian, this is a useful list, but please sort it by Maintainer or by Packa
>ge
>> rather than by bug number:
>
>Several people have asked for this, but maintainers already get separate
>reports about their packages and reports by package are available on
>the
On Fri, May 01, 1998 at 12:38:24PM -0400, Brian White wrote:
> > Brian, this is a useful list, but please sort it by Maintainer or by Package
> > rather than by bug number:
>
> Several people have asked for this, but maintainers already get separate
> reports about their packages and reports by pa
> Brian, this is a useful list, but please sort it by Maintainer or by Package
> rather than by bug number:
Several people have asked for this, but maintainers already get separate
reports about their packages and reports by package are available on
the web site, so I don't really understand the u
12 matches
Mail list logo
