On Tue, 4 Dec 2012 18:51:36 +
Markos Chandras hwoar...@gentoo.org wrote:
Bug-wranglers are supposed to do that by default. When you see a
non-gentoo developer in metadata.xml, the default action is to assume his is
the real maintainer and the bugs should be assigned to him. Such
guidance
On 5 December 2012 02:51, Markos Chandras hwoar...@gentoo.org wrote:
On 4 December 2012 17:28, Rick Zero_Chaos Farina zeroch...@gentoo.org
wrote:
On 12/04/2012 12:06 PM, Diego Elio Pettenò wrote:
Or maybe we can just agree that common sense rules all, and we always
set the proxied
On 6 December 2012 11:02, Ben de Groot yng...@gentoo.org wrote:
On 5 December 2012 02:51, Markos Chandras hwoar...@gentoo.org wrote:
On 4 December 2012 17:28, Rick Zero_Chaos Farina zeroch...@gentoo.org
wrote:
On 12/04/2012 12:06 PM, Diego Elio Pettenò wrote:
Or maybe we can just agree
Markos Chandras wrote:
This policy is for the bug-wranglers project, which someone must
read before he attempts to do any bug-wrangling.
I see no reason to move this to devmanual.
The reason is that I as a developer (whenever I become one) want to
be able to fix stuff right now that is broken
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/12/12 10:27 AM, Peter Stuge wrote:
[ Snip! ] In the last 15 hours I've dealt with several trivial bugs
that I've found fixes for in bugzilla but which were not committed
anywhere.
I've committed them to my overlay and that's fine for me,
Ian Stakenvicius wrote:
Essentially, if the problem is with the ebuild or the way the package
is integrated into gentoo, then fixing it immediately is fine. If the
problem is with the software itself, then usually upstream needs to be
involved before the fix will occur in gentoo.
Yes that's
On 6 December 2012 15:27, Peter Stuge pe...@stuge.se wrote:
Markos Chandras wrote:
This policy is for the bug-wranglers project, which someone must
read before he attempts to do any bug-wrangling.
I see no reason to move this to devmanual.
The reason is that I as a developer (whenever I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/04/2012 12:06 PM, Diego Elio Pettenò wrote:
On 04/12/2012 08:01, Rick Zero_Chaos Farina wrote:
I feel the description field is already overloaded when there is a proxy
situation, maybe it would be best to define a field for this. Also
On 04/12/2012 10:35, Sergey Popov wrote:
Agreed. I add description field to metadata for proxying packages, cause
i see such field in other packages' metadata. That is it. But it would
be better when this became official policy. At least - define actual
maintainer first, even if he is not
On 4 December 2012 17:28, Rick Zero_Chaos Farina zeroch...@gentoo.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/04/2012 12:06 PM, Diego Elio Pettenò wrote:
On 04/12/2012 08:01, Rick Zero_Chaos Farina wrote:
I feel the description field is already overloaded when there is a
10 matches
Mail list logo
