On Wed, Nov 7, 2012 at 5:01 PM, Andreas Tille wrote:
> Right, but solving half of the problem could be easily done asking
> alioth admins for properly setting ACLs for all DDs.
You don't even need to involve the alioth admins, the web interface
for project admins allows adding all members of the
Hi Alioth admins,
please set ACLs as described in [1] for all Git repositories of the
collab-qa team to enable commit permissions to every DD.
Kind regards and thanks for maintaining alioth
Andreas.
[1]
http://wiki.debian.org/Alioth/FAQ#How_do_I_give_write_permission_outside_my_Alioth
On 07/11/12 at 10:01 +0100, Andreas Tille wrote:
> On Wed, Nov 07, 2012 at 08:47:44AM +0100, Lucas Nussbaum wrote:
> > Regarding commit access for all DDs, that only solves half of the
> > problem, since someone would still have to 'git pull' at some point.
>
> Right, but solving half of the probl
On Wed, Nov 07, 2012 at 09:26:28AM +0100, Raphael Hertzog wrote:
> (Dropping the bug)
>
> On Tue, 06 Nov 2012, Steve Langasek wrote:
> > Private mails should not be a justification for expedited orphaning of
> > packages. With this bug report you have *now* used a proper channel for
> > notifying
On Wed, Nov 07, 2012 at 08:47:44AM +0100, Lucas Nussbaum wrote:
> Regarding commit access for all DDs, that only solves half of the
> problem, since someone would still have to 'git pull' at some point.
Right, but solving half of the problem could be easily done asking
alioth admins for properly s
(Dropping the bug)
On Tue, 06 Nov 2012, Steve Langasek wrote:
> Private mails should not be a justification for expedited orphaning of
> packages. With this bug report you have *now* used a proper channel for
> notifying the maintainer that you want to salvage the package; so the clock
> starts n
6 matches
Mail list logo
