public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thilo Bangert <bangert@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Python-3.2-related changes
Date: Tue, 9 Feb 2010 09:10:26 +0100	[thread overview]
Message-ID: <201002090910.29098.bangert@gentoo.org> (raw)
In-Reply-To: <201002081329.52214.Arfrever@gentoo.org>

[-- Attachment #1: Type: Text/Plain, Size: 1238 bytes --]

Arfrever Frehtes Taifersar Arahesis <Arfrever@gentoo.org> said:
> 2010-02-06 17:54:10 Mark Loeser napisał(a):
> > Arfrever Frehtes Taifersar Arahesis <Arfrever@gentoo.org> said:
> > > 2010-02-05 17:40:00 Arfrever Frehtes Taifersar Arahesis napisał(a):
> > > > I consider filing bugs for not adjusted packages after some
> > > > months (e.g in summer).
> > >
> > > 1123 packages (440 in dev-python category) from 108 categories
> > > specify dev-lang/python or virtual/python in DEPEND or RDEPEND, so
> > > actually it might be better to start filing bugs in this month. If
> > > there are no objections, then I would like to file 1 bug per
> > > category (except dev-python category).
> >
> > Make trackers and make one bug per package.  Its way too hard to
> > follow a huge metabug with a bunch of packages listed in it.
> 
> Average number of non-dev-python packages handled in 1 bug would be
>  only 6.4, but I can create create 1 bug per package, if you still want
>  it.

having done mass-filings with one bug per package in the past i know how 
tedious these are.  nevertheless, 1 package per bug it must be - it makes 
all kinds of stuff way easier (think of retirements).

good luck and thanks.
Thilo

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-02-09  8:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05 16:40 [gentoo-dev] Python-3.2-related changes Arfrever Frehtes Taifersar Arahesis
2010-02-06 10:23 ` Arfrever Frehtes Taifersar Arahesis
2010-02-06 16:54   ` Mark Loeser
2010-02-08 12:29     ` Arfrever Frehtes Taifersar Arahesis
2010-02-09  8:10       ` Thilo Bangert [this message]
2010-02-09 11:14         ` [gentoo-dev] " Duncan
2010-02-06 11:03 ` [gentoo-dev] " Arfrever Frehtes Taifersar Arahesis
2010-02-06 12:14   ` Brian Harring
2010-02-08 16:06     ` Arfrever Frehtes Taifersar Arahesis
2010-02-07 18:43   ` Markos Chandras
2010-02-08 12:14     ` Arfrever Frehtes Taifersar Arahesis
2010-02-07 20:17   ` Zac Medico
2010-02-08  0:20     ` Brian Harring
2010-02-08 12:11       ` Arfrever Frehtes Taifersar Arahesis
2010-03-01  3:13 ` Arfrever Frehtes Taifersar Arahesis
2010-03-01  5:13   ` Max Arnold
2010-03-01 23:06     ` Arfrever Frehtes Taifersar Arahesis

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=201002090910.29098.bangert@gentoo.org \
    --to=bangert@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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