[pyelftools/f19] (4 commits) ...python3 is not available in epel7
moez.roy at gmail.com
Fri Oct 10 05:57:41 UTC 2014
On Thu, Oct 9, 2014 at 2:52 PM, Orion Poplawski <orion at cora.nwra.com> wrote:
> On 10/08/2014 11:41 PM, Moez Roy wrote:
> > Summary of changes:
> > 58461a8... Rebuilt for https://fedoraproject.org/wiki/Changes/Python_3 (*)
> > 7ec9589... - Rebuilt for https://fedoraproject.org/wiki/Fedora_21_Mass (*)
> > f0aeace... - Rebuilt for https://fedoraproject.org/wiki/Fedora_21_22_M (*)
> > 360daf2... python3 is not available in epel7 (*)
> > (*) This commit already existed in another branch; no separate mail sent
> FWIW - I don't see any reason to push these commit to the stable branches
> unless you are actually making a change that affects them and building/pushing
> a new update.
> Orion Poplawski
> Technical Manager 303-415-9701 x222
> NWRA, Boulder/CoRA Office FAX: 303-415-9702
> 3380 Mitchell Lane orion at nwra.com
> Boulder, CO 80301 http://www.nwra.com
> devel mailing list
> devel at lists.fedoraproject.org
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
The reason I did that was so that all the branches stay in sync.
Especially when there is a new update, the git merge master won't give
any merge conflicts (which will require me to rebase the other
branches to master).
Is there a reason not to do it?
More information about the devel