fweimer added a new comment to an issue you are following: `` We already have to do these weird transformations today because tarball + patches is so burdensome. I would even suggest that it discourages upstream work: First, we spent effort instead on shoehorning Git repositories into Fedora, time which could be used more productively. Second, if we have a downstream patch, upstreaming it will introduce a conflict, which is generally difficult to resolve with the basic tarball+patches tooling that RPM provides.
Eventually, I want to use Git-based tooling (whether it's Gerrit or Pagure, we'll see) and remove a random developer workstation from the release process, where a crucial step is performed (tarball generation), which is difficult to review at the Git level. In addition, for Fedora at least, I want to use actual merges from upstream to bring in upstream changes, rather than serializing everything into a list of patches.
I also want to use the same process in Fedora glibc and downstream, so that less developer training is needed. Downstream, we have hundreds of backported patches. In Fedora 28, we currently have 53 upstream patches since the release, plus the Fedora-specific patches. For Fedora 27, we will soon have 146 upstream patches. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7498