Date: Sat, 13 Jan 2007 21:54:11 +0100 From: Alexander Leidinger <Alexander@Leidinger.net> To: "Andrew Pantyukhin" <infofarmer@FreeBSD.org> Cc: emulation@freebsd.org, Mark Linimon <linimon@lonesome.com> Subject: Re: Overlong mailing-list maintainer address in ports Message-ID: <20070113215411.6a80a04f@Magellan.Leidinger.net> In-Reply-To: <cb5206420701131215i531e3c16m44198ee2985454f6@mail.gmail.com> References: <cb5206420612231103v69d1780dlefb3d4c62ca10baa@mail.gmail.com> <21940630@bsam.ru> <cb5206420612231234w1b01c0bbgc61f4e8f7827e455@mail.gmail.com> <20061223211725.GB24163@soaustin.net> <20061224120420.0542dfdb@Magellan.Leidinger.net> <20061224113035.GA25941@soaustin.net> <cb5206420701131215i531e3c16m44198ee2985454f6@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting "Andrew Pantyukhin" <infofarmer@FreeBSD.org> (Sat, 13 Jan 2007 23:15:33 +0300): > On 12/24/06, Mark Linimon <linimon@lonesome.com> wrote: > > On Sun, Dec 24, 2006 at 12:04:20PM +0100, Alexander Leidinger wrote: > > > If I read this right: in Makefiles we should use emulation@FreeBSD.org > > > and in PRs freebsd-emulation, right? > > > > Checking the existing ports, they are all assigned to freebsd-emulation@. > > Right. The question is, should we stick to shorter > form for maintainership or allow both forms being > used on a case-by-case basis. If you use both kinds of addressing you create 2 maintenance groups in automated tools (portsmon, automated PR mailing, ...). This can be used on purpose, but is highly confusing to people which don't use this on a daily basis (= confusing to people which have ot assign a PR to the right group). Bye, Alexander. -- Yes! Oh, yes! Read it and weep! In your face -- I got more chicken bone! -- Homer Simpson When Flanders Failed http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070113215411.6a80a04f>