On 7/19/17, Yuri Gribov wrote:
> On Wed, Jul 19, 2017 at 7:15 PM, Eric Gallager
> wrote:
>> On 7/18/17, Yuri Gribov wrote:
>>> On Tue, Jul 18, 2017 at 3:54 PM, Martin Sebor wrote:
On 07/17/2017 02:25 PM, Yuri Gribov wrote:
>
> On Mon, Jul 17, 2017 at 4:23 PM, Martin Sebor
> wr
On Wed, Jul 19, 2017 at 7:15 PM, Eric Gallager wrote:
> On 7/18/17, Yuri Gribov wrote:
>> On Tue, Jul 18, 2017 at 3:54 PM, Martin Sebor wrote:
>>> On 07/17/2017 02:25 PM, Yuri Gribov wrote:
On Mon, Jul 17, 2017 at 4:23 PM, Martin Sebor wrote:
>
> On 07/17/2017 02:14 AM, Yuri G
On 19 July 2017 at 19:15, Eric Gallager wrote:
> On 7/18/17, Yuri Gribov wrote:
>> Jonathan also mentioned something not immediately obvious in IRC:
>> logging into BZ with gcc.gnu.org account provides elevated privileges.
>> So if you have write access, you should get extra BZ rights for free.
>>
On 7/18/17, Yuri Gribov wrote:
> On Tue, Jul 18, 2017 at 3:54 PM, Martin Sebor wrote:
>> On 07/17/2017 02:25 PM, Yuri Gribov wrote:
>>>
>>> On Mon, Jul 17, 2017 at 4:23 PM, Martin Sebor wrote:
On 07/17/2017 02:14 AM, Yuri Gribov wrote:
>
>
> Hi Mikhail,
>
> On Sun,
On 18 July 2017 at 16:32, Yuri Gribov wrote:
> Jonathan also mentioned something not immediately obvious in IRC:
> logging into BZ with gcc.gnu.org account provides elevated privileges.
> So if you have write access, you should get extra BZ rights for free.
We should document this at https://gcc.g
On Tue, Jul 18, 2017 at 3:54 PM, Martin Sebor wrote:
> On 07/17/2017 02:25 PM, Yuri Gribov wrote:
>>
>> On Mon, Jul 17, 2017 at 4:23 PM, Martin Sebor wrote:
>>>
>>> On 07/17/2017 02:14 AM, Yuri Gribov wrote:
Hi Mikhail,
On Sun, Jul 2, 2017 at 6:39 PM, Mikhail Maltsev
>>>
On 07/17/2017 02:25 PM, Yuri Gribov wrote:
On Mon, Jul 17, 2017 at 4:23 PM, Martin Sebor wrote:
On 07/17/2017 02:14 AM, Yuri Gribov wrote:
Hi Mikhail,
On Sun, Jul 2, 2017 at 6:39 PM, Mikhail Maltsev
wrote:
Hi. Yes, bug maintenance is appreciated. See this message and replies
to it: https:
On 17 July 2017 at 21:25, Yuri Gribov wrote:
> What to do about bugs originating in upstream packages? I noticed
> they sometimes get closed with "RESOLVED MOVED" resolution
> (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58841) but often this
> does not happen and they just hang in tracker foreve
On 07/17/2017 10:33 PM, NightStrike wrote:
> On Mon, Jul 17, 2017 at 11:23 AM, Martin Sebor wrote:
>> you did for the bugs below is ideal. Adding a test case if one
>> doesn't exist in the test suite is also very useful, though quite
>> a bit more work.
>
> Isn't a testcase always required?
Requ
On Mon, Jul 17, 2017 at 11:23 AM, Martin Sebor wrote:
> you did for the bugs below is ideal. Adding a test case if one
> doesn't exist in the test suite is also very useful, though quite
> a bit more work.
Isn't a testcase always required?
On Mon, Jul 17, 2017 at 4:23 PM, Martin Sebor wrote:
> On 07/17/2017 02:14 AM, Yuri Gribov wrote:
>>
>> Hi Mikhail,
>>
>> On Sun, Jul 2, 2017 at 6:39 PM, Mikhail Maltsev
>> wrote:
>>>
>>> Hi. Yes, bug maintenance is appreciated. See this message and replies
>>> to it: https://gcc.gnu.org/ml/gcc/2
On 07/17/2017 02:14 AM, Yuri Gribov wrote:
Hi Mikhail,
On Sun, Jul 2, 2017 at 6:39 PM, Mikhail Maltsev wrote:
Hi. Yes, bug maintenance is appreciated. See this message and replies
to it: https://gcc.gnu.org/ml/gcc/2016-04/msg00258.html .
Replies in your link suggest to leave a final comment
Hi Mikhail,
On Sun, Jul 2, 2017 at 6:39 PM, Mikhail Maltsev wrote:
> Hi. Yes, bug maintenance is appreciated. See this message and replies
> to it: https://gcc.gnu.org/ml/gcc/2016-04/msg00258.html .
Replies in your link suggest to leave a final comment in bugs with
explanatory suggestion to clos
On 07/02/2017 11:08 AM, Yuri Gribov wrote:
> Hi all,
>
> What do I need to do to close an old bug which does not repro with
> modern GCC and reporter does not care anymore (e.g.
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40528)? Also, is there
> some general policy about closing old bugs?
Idea
Hi. Yes, bug maintenance is appreciated. See this message and replies
to it: https://gcc.gnu.org/ml/gcc/2016-04/msg00258.html .
I'm not sure that there is a documented policy, but I might be wrong.
--
Regards,
Mikhail Maltsev
Hi all,
What do I need to do to close an old bug which does not repro with
modern GCC and reporter does not care anymore (e.g.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40528)? Also, is there
some general policy about closing old bugs?
-Y
16 matches
Mail list logo
