-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 8/4/10 3:01 PM, M A Young wrote: > What is the policy on creating private branches under fedpkg/git? Can it > be done by anyone with acl commit or do you need special permissions? > > My interest is that I had a private branch of the kernel package under CVS > which I used to build pvops enabled kernels so that the more adventurous > could use a Fedora based Domain-0 kernel with xen. However this branch > hasn't been copied across (presumably because of the difficulties in > transfering the kernel package) though I could easily continue from a new > branch if that is appropriate. > > Michael Young The way it works now, if a maintainer has at least commit access to the master branch (eg rawhide) they can create any top level branches they want, so long as it doesn't conflict with the naming scheme of our release branches (f??/master, el?/master, olpc?/master). Outside of that, if you have commit access to a specific branch, but not master, you are allowed to create branches within that name space, eg if you have commit rights to f13 but not master, you can create branches under f13/<branchname>. Again you cannot conflict with f13/master. However, since git allows you to create local branches at will without any restrictions, one has to ask if it is still necessary to have a remote branch for your work. - -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxsKUQACgkQ4v2HLvE71NXpMQCeMPidJkbFTsFOIffaGRXgcIPc Hx8AoJLVsPgIFoovTrgc4K/xjsYrWkC9 =WpXr -----END PGP SIGNATURE----- -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
