nim commented on the pull-request: `make it use the actual code that was merged 
in redhat-rpm-config-130` that you are following:
``
Ah, that

Just because it is trivial does not mean stupid typos can not happen, so the 
commits cook in a private feature branch (where I can rewrite git history 
without bothering anyone) and are merged when they pass testing.

The commit state that get merged is rarely the first version I wrote.

Is there a simpler/better method to move reliably a set of commits from a 
forked feature branch to the main project?
``

To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/16
_______________________________________________
golang mailing list -- golang@lists.fedoraproject.org
To unsubscribe send an email to golang-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/golang@lists.fedoraproject.org

Reply via email to