On Fri, 23 Jan 2026 07:29:31 -0700 Warner Losh <[email protected]> wrote:
> On Fri, Jan 23, 2026 at 7:16 AM Mark Linimon <[email protected]> wrote: > > > > On 01/23/2026 3:21 AM CST Tomoaki AOKI <[email protected]> > > wrote: > > > I think opening review on Phabricator alone is easily missed. > > > So I basically file a PR on Bugzilla, open review and introduce > > > the D number of the review on Bugzilla PR. > > > > IMHO the fact that we make our developers jump through these hoops > > is proof our tooling is wrong. > > > > Yes. 100% agreed. It's the tooling we have. It's not the tooling we want. > there are too many hoops. > > > > Other than duplicating work, he biggest problem with the workflow > > above is that Someone (TM) needs to go through the Problem Reports > > looking for references to completed DR. > > > Yes. Also a flaw. It's also why we need to strongly say 'do not duplicate' > because > It causes nothing but extra work for us and has limited value. > > Warner I file a bug for regular users that are not familiar with Phabricator. Currently official GitHub mirror does't make "issues" feature enabled, so Bugzilla is the only bug tracker for non-developer users to report bugs / request features without supplying patches. But yes, Bugzilla is not good at "code reviews". So I open reviews, too, when I have patches. But for infrastructual changes that non-developer users wouldn't be affected, I don't file bugs and open reviews only. So I'm looking forward that forgejo repo become official mirror and unifying workflow possible. BTW, the account I've registered at Forgejo repo seems to be deleted. Regards. -- Tomoaki AOKI <[email protected]>
