On 13 September 2015 at 09:15, hasufell <hasuf...@gentoo.org> wrote: > Because that is not a valid bug report. Patches must be attached to > bugzilla.
I would recommend against attaching the pull in patch form against bugzilla. It might lead to unintentionally misleading consequences. If the patch is automatedly filed against bugzilla, people will assume viewing that patch tells them all they need to know. But the reality is somebody may rebase/amend/repush to the publicised branch location before any developer reviews the patch in bugzilla, and so by the time somebody reviews the patch, it is already wrong. And as it is common for there to be a "get feedback, amend the pull, get feedback, amend the pull" loop in existing real-world git workflows, it should be assumed that is going to happen frequently. It would also be better for there to be some way to specify a repository remote and a ref-spec, not having github-intrinsic behaviours. ( Because people may have personally hosted git repos they want feedback on if they have a github aversion, and we must not *require* github to interact with the development workflow ) -- Kent KENTNL - https://metacpan.org/author/KENTNL
