-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear all, When submitting a package change request for a new branch, the new branch is currently instantiated with the revision history of the master (development) branch. When the new branch created is for an EPEL release, this might not be appropriate -- for instance, I just asked for python-psutil to be branched; master is at 0.6.1, el6 is at 0.4.1 and now the new el5 branch is at 0.6.1. Is there an interest in an improvement in which one can specify which commit (or, simpler but less flexible, which branch head) to use when instantiating each particular branch)? (and where should this be filed - - as a rel-eng request in Trac, presumably) Thanks, - -- Michel Alexandre Salim Fedora Project Contributor: http://fedoraproject.org/ Email: salimma@xxxxxxxxxxxxxxxxx | GPG key ID: A36A937A Jabber: hircus@xxxxxxxxxxxxx | IRC: hircus@xxxxxxxxxxxxxxxx () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRR+9tAAoJEEr1VKujapN6IhcIAIrGEHQ1YyCk3h2fw9Mogfan jCovrumnA2WavqxMyXOvk/g2Io8SOZuGnH5YfQ+TvXgu6CEWG58UDKy/p2dfGwC9 pXAe8VIkG9rcz4QEiSboh9AIb+Cg9GFLkwjBd3w5kMnLrPhr2m20mXjvQ0UjIZaX WNic+gYIYToQvVygl7KkN4Xqvr/1obvDQWcx0TcQd423G1wXip0n38nVA4VjnQ7C HbKLLiiOms0b0l6LA+3M5mG+L9dnnRbM5uLidKTTvVTchL4lY/UJKaFpfYF09oLP N5FLYj7l9gA0UZozbYqNtWMLDqZ3+L/6vUfdiLi491a8WmOxyIk2kwa0FLchLxY= =LT4M -----END PGP SIGNATURE----- -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel