so that maintainers could apply them to architecture-specific bugs when
necessary. The format, suggested by Steve Langasek, was to use the
porters mailinglist as the user, and the architecture name as the
usertag (e.g., 'debian-m...@lists.debian.org' as user, and 'm68k' as
tag).
Armel has alread
On Tue, Mar 03, 2009 at 08:52:03PM +0100, Wouter Verhelst wrote:
> so that maintainers could apply them to architecture-specific bugs when
> necessary. The format, suggested by Steve Langasek, was to use the
> porters mailinglist as the user, and the architecture name as the
> usertag (e.g., 'debia
On Tue, Mar 03, 2009 at 08:52:03PM +0100, Wouter Verhelst wrote:
> After a short discussion on IRC, we came up with another option: a set
> of publically documented usertags, the definition of which would be
> announced on debian-devel-announce and linked to from the BTS homepage,
> so that maintai
On Thu, Mar 05, 2009 at 11:22:19AM +0100, Peter Palfrader wrote:
> On Tue, 03 Mar 2009, Wouter Verhelst wrote:
>
> >The format, suggested by Steve Langasek, was to use the
> > porters mailinglist as the user, and the architecture name as the
> > usertag (e.g., 'debian-m...@lists.debian
On Tue, 03 Mar 2009, Wouter Verhelst wrote:
>The format, suggested by Steve Langasek, was to use the
> porters mailinglist as the user, and the architecture name as the
> usertag (e.g., 'debian-m...@lists.debian.org' as user, and 'm68k' as
> tag).
Or debian-po...@lists.debian.org as u
On Tue, Mar 03, 2009 at 10:03:18PM +0200, Vasilios Karaklioumis wrote:
> Wouter Verhelst wrote:
>> Hi,
>>
>> I've often thought that it would be useful to have tags in the BTS so
>> that users or maintainers could mark a bug as specific to a particular
>> architecture. This way, when I have some sp
Wouter Verhelst wrote:
Hi,
I've often thought that it would be useful to have tags in the BTS so
that users or maintainers could mark a bug as specific to a particular
architecture. This way, when I have some spare time, I could go to the
BTS, fetch a list of bugs that are specific to an archite
Hi,
I've often thought that it would be useful to have tags in the BTS so
that users or maintainers could mark a bug as specific to a particular
architecture. This way, when I have some spare time, I could go to the
BTS, fetch a list of bugs that are specific to an architecture I care
about, and s
8 matches
Mail list logo