On Mon, 25 Jan 2021 at 13:58, Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx> wrote:
On Mon, Jan 25, 2021 at 01:42:17PM -0500, Stephen John Smoogen wrote:
> On Mon, 25 Jan 2021 at 13:30, Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx>
> wrote:
> >
> If this was some other code which was tied into some sort of continuous
> rebuild system, wouldn't the developer strategy be that you would push the
> changes to a branch which wasn't rebuilt, test that and then pull the fixes
> in. I am not talking about fork and pr.. I am just thinking branch and pull
> which should be scriptable in even a 10k package ownership method.
>
> say something like
>
> for X in packages
> fedpkg temp-scratch -b scratch-fedora
fedpkg 'temp-branch' is just an idea, right? Normally branches in
dist-git are semi-permanent and require a releng ticket to be removed.
Just an idea with syntax to give people something to work from. I forgot that part which makes it less likely to be possible
--
Stephen J Smoogen.
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
