Thanks... I wasn't sure about that (probably should've asked first), but I couldn't *recall* seeing them in other package changelog history. I'll leave them alone in the future.
Is there a typical pattern for updating the various branches for a package? https://rpmfusion.org/Contributors#Updating_an_existing_package is kind of silent on that point. It only really ever mentions branches in passing, and never explicitly addresses any procedures to perform operations between them. I ended up fast-forward merging master -> f28 -> f27 (because the updated .spec / patches were only present in master, at the start), but that felt a bit weird and carried the rebuild messages back into the package changelogs for earlier releases. On Thu, Aug 9, 2018 at 8:53 AM Nicolas Chauvet <[email protected]> wrote: > FYI, > Please avoid to remove theses notes in branches, this is totally > spurious and will break fast-forward merge between branches. > > Thx > Le jeu. 9 août 2018 à 12:33, Frank R Dana <[email protected]> a écrit > : > > > > Summary of changes: > > > > 3359caf... Rebuilt for Python 3.7 (*) > > b475156... - Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass > (*) > > 687d6e8... New upstream release (*) > > 291afab... Uploaded source (*) > > aa0a3f3... remove F29 rebuild note > > > > (*) This commit already existed in another branch; no separate mail sent > > _______________________________________________ > > rpmfusion-commits mailing list -- [email protected] > > To unsubscribe send an email to > [email protected] > > > > -- > - > > Nicolas (kwizart) >
_______________________________________________ rpmfusion-developers mailing list -- [email protected] To unsubscribe send an email to [email protected]
