On Tue, Nov 19, 2013 at 12:14:42PM +0000, Richard W.M. Jones wrote: > On Tue, Nov 19, 2013 at 12:51:29PM +0100, Karel Zak wrote: > > On Tue, Nov 19, 2013 at 10:51:01AM +0000, Daniel P. Berrange wrote: > > > Yep, I've done the same thing for all the packages I maintain in Fedora > > > and RHEL too. It makes maintaining RPMs soo much easier, particularly > > > when you have lots of patches to manage. The script I use is > > > > > > http://pkgs.fedoraproject.org/cgit/libvirt-sandbox.git/tree/update-patches.pl > > > > Cool. > > > > It would be nice to improve the script to read "References:" or > > "Addresses:" lines from the git commit messages and use the lines as > > comments for Patch%d: in the SPEC file. Something like: > > > > # https://bugzilla.redhat.com/show_bug.cgi?id=850355 > > Patch123: 0001-foo-bar.patch > > > > Maybe it would be also possible to use the URL to ask bugzilla for > > bug Id and Subject and then generate SPEC %changelog :-) > > The erlang patches script also reads various information from the > commit comments too. We have to learn fedpkg to do all the magic ;-) Something like add remote git tree with exploded tree: fedpkg exploded-tree add ssh://git.fedorahosted.org/git/foo.git list log for exploded/upstream..exploded/f20 (or only --new commits which not found in .spec): fedpkg exploded-tree log [--new] generate Patch<N>: .spec file lines, call git format-patch and git-add from exploded/upstream..exploded/f20 stuff: fedpkg exploded-tree update-patches generate %changelog according to References: from commit messages: fedpkg exploded-tree update-changelog ... dreaming is so simple, volunteers? :-) Karel -- Karel Zak <kzak@xxxxxxxxxx> http://karelzak.blogspot.com -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
