On Mon, 21 Dec 2009 18:59:53 -0800
Josh Stone <jistone@xxxxxxxxxx> wrote:
> On 12/21/2009 06:10 PM, Jesse Keating wrote:
> > This has been done. The way the ACLs now work, if you are a
> > packager, you can create branches in any package that start with
> > "private-". This makes it even easier to pass changes around as
> > you can tell the maintainer to pull from or merge from a private
> > branch you've created.
>
> Perhaps this should be locked down to private-$USERNAME-*? Otherwise,
> anyone could push into a branch that I'm trying to work with.
Good catch IMHO. My first thought also would be to separate the
branches the package (co-)maintainers create, and those that
every contributor can create to reduce conflicts. However, I would
try to make them distinguishable, e.g.:
private-foo
for branches where all people in the pkg ACLs can push to
private/${FAS_ACCOUNT}/*
for the "any contributor can push" branches
Having private-foo-baar for feature foo-bar and private-foo-bar for user
foo's bar branch could end up being quite confusing.
--
Hans Ulrich Niedermann
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
