On Tue, 2019-01-29 at 15:15:18 +0000, Debian Bug Tracking System wrote: > Date: Tue, 29 Jan 2019 16:12:01 +0100 > From: Thomas Goirand <z...@debian.org> > To: 920745-d...@bugs.debian.org > Subject: Re: Bug#920745: git-review: Make --yes configurable > Message-ID: <35a6fd63-346b-4ab7-c84d-e8de4cdae...@debian.org> > User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 > Thunderbird/60.4.0 > X-Spam-Status: No, score=-17.6 required=4.0 tests=BAYES_00,FROMDEVELOPER, > HAS_BUG_NUMBER,MURPHY_DRUGS_REL8,RCVD_IN_DNSWL_NONE,TXREP autolearn=ham > autolearn_force=no version=3.4.2-bugs.debian.org_2005_01_02 > > On 1/28/19 6:04 PM, Guillem Jover wrote: > > Package: git-review > > Version: 1.26.0-1 > > Severity: wishlist
> > I find myself very often sending multiple patches for review, and then > > coming back to that terminal after a while to see the --yes promp > > waiting there. > > > > It would be nice to have --yes be settable via a configuration option, > > so that it can be enabled all the time. > Thanks for this remark. > > I have forwarded your issue to the upstream bug tracker: > https://storyboard.openstack.org/#!/story/2004886 > > At this point, there's nothing more I can do, as I don't work on the > upstream code. Therefore, I'm just closing this bug. Hopefully, you can > continue on discussing this with upstream, or propose a patch yourself. Wait what? :) It seems you acknowledged the request, even forwarding it upstream (thanks for that!), but then close it in Debian when it's not been resolved there one way or another (say fixed or wontfixed?). The normal way to handle this would be to do the following instead: Control: reopen -1 Control: tag -1 upstream Control: forwarded -1 https://storyboard.openstack.org/#!/story/2004886 Thanks, Guillem
