On 12/08/2017 02:40 PM, Steve Dickson wrote:
Hey,
On 12/07/2017 02:31 PM, Florian Weimer wrote:
On 12/07/2017 04:31 PM, Steve Dickson wrote:
Where committed to the master branch and not to any other
branch make the maintenance of those branches a pain
because I can no longer cherry-pick between branches.
Maybe you can elaborate on how this causes problems for your
development process, and we can find a way to avoid that?
I think the best way to avoid these problems is have any all changes
go through the maintainer...
That doesn't work if the maintainer doesn't react in a timely fashion to
bug reports, as it is the case for many maintainers unfortunately. For
non-critical issues, this is quite understandable, too.
If cleanups have to go through the maintainer, it's pretty much like
saying that they should not happen, ever.
Now when something breaks from a change like this... Who are you going to call? :-)
Not the Ghostbusters... the maintainer and if the maintainer didn't even know
about the change... how fair that??
I don't understand the problem. If the change came with an upstream
import, most maintainers would be surprised as well (because they are
not upstream or have not reviewed any single upstream change).
Again, if there is a Git proces issue here, we can provide guidelines to
avoid that with bulk changes (and perhaps a minor Koji enhancement on
top). But if you don't say what the technical problems are that you are
dealing with, we can't make such improvements.
Thanks,
Florian
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
