On 11/21/18 1:43 AM, Martin Sebor wrote:
> On 11/20/2018 03:08 AM, Martin Liška wrote:
>> Hi.
>>
>> It's the script that I used to identify potentially resolvable bugs. That's
>> done
>> by parsing of comments and seeking for trunk/branch commits. Sample output
>> looks
>> as follows:
>>
>> htt
On Tue, 2018-11-20 at 11:08 +0100, Martin Liška wrote:
> Hi.
>
> It's the script that I used to identify potentially resolvable bugs.
> That's done
> by parsing of comments and seeking for trunk/branch commits. Sample
> output looks
> as follows:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id
On 11/20/2018 03:08 AM, Martin Liška wrote:
Hi.
It's the script that I used to identify potentially resolvable bugs. That's done
by parsing of comments and seeking for trunk/branch commits. Sample output looks
as follows:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88084 branches: trunk
On 11/20/18 3:08 AM, Martin Liška wrote:
> Hi.
>
> It's the script that I used to identify potentially resolvable bugs. That's
> done
> by parsing of comments and seeking for trunk/branch commits. Sample output
> looks
> as follows:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88084 branc
Hi.
It's the script that I used to identify potentially resolvable bugs. That's done
by parsing of comments and seeking for trunk/branch commits. Sample output looks
as follows:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88084 branches: trunk
fail: