gotmax23 opened a new pull-request against the project: `go-rpm-macros` that you are following: `` Introduce %golang_arches_future and stop using %go_arches ``
To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/pull-request/48
gotmax23 commented on the pull-request: `Introduce %golang_arches_future and stop using %go_arches` that you are following: `` Related PRs:
- distgit repo: https://src.fedoraproject.org/rpms/go-rpm-macros/pull-request/8 - go2rpm: https://pagure.io/GoSIG/go2rpm/pull-request/21 ``
To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/pull-request/48
eclipseo commented on the pull-request: `Introduce %golang_arches_future and stop using %go_arches` that you are following: `` lgtm, although, won't we need to go back to all the -f created once we are out of ix86 completely? ``
To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/pull-request/48
gotmax23 commented on the pull-request: `Introduce %golang_arches_future and stop using %go_arches` that you are following: ``
lgtm, although, won't we need to go back to all the -f created once we are out of ix86 completely?
That or make it no-op and print deprecation warnings. I think we can cross that bridge when we come to it. ``
To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/pull-request/48
gotmax23 commented on the pull-request: `Introduce %golang_arches_future and stop using %go_arches` that you are following: ``
lgtm, although, won't we need to go back to all the -f created once we are out of ix86 completely?
That or make it no-op and print deprecation warnings. I think we can cross that bridge when we come to it. ``
To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/pull-request/48
gotmax23 commented on the pull-request: `Introduce %golang_arches_future and stop using %go_arches` that you are following: ``
lgtm, although, won't we need to go back to all the -f created once we are out of ix86 completely?
That or make it no-op and print deprecation warnings. I think we can cross that bridge when we come to it. ``
To reply, visit the link below or just reply to this email https://pagure.io/go-rpm-macros/pull-request/48
gotmax23 merged a pull-request against the project: `go-rpm-macros` that you are following.
Merged pull-request:
`` Introduce %golang_arches_future and stop using %go_arches ``
golang@lists.fedoraproject.org