V Tue, May 24, 2022 at 01:16:44PM +0200, Michal Schorm napsal(a): > Beside that, the > | fedpkg request-branch -h > doesn't explain what will be the content of the newly created branch. > It belive that it behaves the same as requesting a branch for a non-modular content. E.g. when requesting an EPEL branch. It will contain an initial empty commit from rawhide branch. Later you can merge commits from other branches as you like. > I also don't understand what happens when in a case of module named > 'X', consisting of RPMs named 'X' and 'Y', I go to the RPM 'Y' and > call the 'fedpkg-request branch' without '--no-auto-module'. > Will that create a new modular repo named 'Y' ? I think now new modular repo will created. What it does is creating "Y" branch in the modular repo. > Will that create a branch with a name I choosed in the modular repo 'X' ? > It will create a branch of a name you passed as an argument to the command. -- Petr
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
