<div dir="ltr">/me wants the ability to push force on *private* branches<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014/1/15 Dridi Boukelmoune <span dir="ltr"><<a href="mailto:dridi.boukelmoune@gmail.com" target="_blank">dridi.boukelmoune@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Wed, Jan 15, 2014 at 2:16 PM, Vít Ondruch <<a href="mailto:vondruch@redhat.com">vondruch@redhat.com</a>> wrote:<br>
> Dne 14.1.2014 21:41, Andrew Lutomirski napsal(a):<br>
>> I have some trivial cleanups I want to make to a package a maintain.<br>
>> These cleanups are trivial enough that I don't think they're worth a<br>
>> new build. Should I commit them to the master branch? If so, I can<br>
>> imagine a couple of issues:<br>
>><br>
>> - A provenpackager could kick off a rebuild for whatever reason (e.g.<br>
>> dependency soname bump). That will (I think) inadvertently include my<br>
>> changes.<br>
>> - I need to think about whether to add a changelog entry or not. If<br>
>> not, those changes might be included silently. If yes, then I need to<br>
>> think about what to do about the revision number.<br>
>><br>
>> The normal GIT approach would be to develop on another branch and to<br>
>> merge when I want to build a new revision (the Fedora equivalent of<br>
>> tagging a new release). Should Fedora provide branches like<br>
>> master-devel, f20-devel, etc that store pending changes?<br>
>><br>
>> Am I missing something really obvious here?<br>
>><br>
>> --Andy<br>
><br>
> Actually I'd really love to see some possibility for private branches.<br>
> Now, it is possible to push whatever branch (take it literally) you have<br>
> in your local git repo into dist-git, but there is no way how to delete<br>
> it by myself.<br>
><br>
> For example, I am using branches to keep my .spec file aligned with<br>
> upstream development and I'd like to share it with other maintainers.<br>
> But this .spec file should never build in Rawhide unless it is approved<br>
> by FESCo.<br>
><br>
> Could you please add support for private branches? I.e. the branch which<br>
> starts by private- prefix could be pushed and deleted as well, non ff<br>
> commit should be allowed. Actually, better would be if only master, fxx<br>
> and elx are protected and others are unrestricted, but I am probably<br>
> asking too much.<br>
<br>
</div></div>For private branches I'd rather see something along fas/branch.<br>
<br>
With the '/' separator you can glob refspecs, and using your fas as a<br>
prefix could enable automatic acls with less pain on the<br>
infrastructure side (eg. allow anyone to manage and own private<br>
branches at will).<br>
<span class="HOEnZb"><font color="#888888"><br>
Dridi<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
> Vít<br>
> --<br>
> devel mailing list<br>
> <a href="mailto:devel@lists.fedoraproject.org">devel@lists.fedoraproject.org</a><br>
> <a href="https://admin.fedoraproject.org/mailman/listinfo/devel" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/devel</a><br>
> Fedora Code of Conduct: <a href="http://fedoraproject.org/code-of-conduct" target="_blank">http://fedoraproject.org/code-of-conduct</a><br>
--<br>
devel mailing list<br>
<a href="mailto:devel@lists.fedoraproject.org">devel@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/devel" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/devel</a><br>
Fedora Code of Conduct: <a href="http://fedoraproject.org/code-of-conduct" target="_blank">http://fedoraproject.org/code-of-conduct</a></div></div></blockquote></div><br></div>