Am 29.01.20 um 09:52 schrieb Cristián Maureira-Fredes:
> I think nobody at Qt will be so irresponsible of not notifying
> security patches, and I'm certain we will work around this issue,
> to maybe distributed in a better way for Open Source users.
Hi Cristián,
what exactly do you consider a
Am 22.11.2019 um 19:11 schrieb Edward Welbourne:
> Il 21/11/19 13:13, Robert Loehning ha scritto:
>>> ** [https://doc.qt.io/qt-5/qregularexpression.html QRegularExpression]
>
> Giuseppe D'Angelo (22 November 2019 18:17) replied:
>> This should mostly be fuzzing libpcre
Hi,
Here and below are the notes from this session:
https://wiki.qt.io/Qt_Contributors_Summit_2019_-Fuzzing_Qt
Cheers,
Robert
== Introduction ==
* Explained briefly what fuzzing is in general
* Showed how to fuzz Qt itselfSee readme file:
Am 01.07.2019 um 19:57 schrieb André Pönitz:
> On Mon, Jul 01, 2019 at 02:43:43PM +, Frederik Gladhorn wrote:
and I'll give Gravatar a spin:
https://gerrit-review.googlesource.com/admin/repos/plugins/avatars-gravata
r
>>
>> It's there, enjoy and put your avatar up at
Am 26.03.2019 um 09:48 schrieb Frederik Gladhorn:
> On fredag 15. mars 2019 14:05:39 CET Robert Loehning wrote:
>> Hi *,
>>
>> imagine the following situation:
>> 1. Bug in 5.13 is reported
>> 2. Patch with "Fixes: " is merged to 5.13 branch
>>
Am 15.03.2019 um 14:38 schrieb Edward Welbourne:
> Robert Loehning (15 March 2019 14:05) wrote:
>> imagine the following situation:
>> 1. Bug in 5.13 is reported
>> 2. Patch with "Fixes: " is merged to 5.13 branch
>> 3. Gerrit Bot closes the report with &qu
Hi *,
imagine the following situation:
1. Bug in 5.13 is reported
2. Patch with "Fixes: " is merged to 5.13 branch
3. Gerrit Bot closes the report with "Fix Version 5.13".
4. Reporter tests 5.13 branch, fix failed, reopens report
5. Patch is merged to dev branch
6. Gerrit Bot finds the patch in
+1 for Ulf.
Disclaimer: He's working for the same company as I do.
Thank you for your work, Simon!
Am 18.02.2019 um 14:25 schrieb Simon Hausmann:
> Hi,
>
> I'd like to step down as the maintainer of the Qt QML module and pass the
> torch on to Ulf Hermann.
>
> He has been contributing to the
Am 28.01.2019 um 14:09 schrieb Jedrzej Nowacki:
> On Friday, January 25, 2019 3:23:36 PM CET Robert Loehning wrote:
>>> Testing whether the bug that I’m fixing exists in dev or not is part of
>>> the drill of fixing bug, isn’t it? Why would you spend time on fixing
>>
Am 28.01.2019 um 13:54 schrieb Volker Hilsheimer:
>> On 28 Jan 2019, at 13:36, Martin Smith wrote:
>>> On 28 Jan 2019, at 13:27, Robert Loehning wrote:
>>>> Am 24.01.2019 um 10:20 schrieb Volker Hilsheimer:
>>>>> On 24 Jan 2019, at 08:03, Oliv
Am 24.01.2019 um 10:20 schrieb Volker Hilsheimer:
>> On 24 Jan 2019, at 08:03, Olivier Goffart wrote:
>> [...]>- Stay with the current solution <= the merge effort is too big
>> and qt6 is
>>> expected to cause conflicts that really should not be solved by one person
>>
>> Again, I don't see
r. To help with that, we can simply run a regular status check
>>> on the repo. If this happens the repo will be blocked for further
>>> testing until someone submits a fix or reverts an offending change,
>>> which is acceptable.
>
> When those events happen, they
Am 25.01.2019 um 11:08 schrieb Lars Knoll:
>
>
> On 25 Jan 2019, at 10:10, Simon Hausmann
> mailto:simon.hausm...@qt.io>> wrote:
>
>
> I think it's worthwhile to develop the tooling to automate cherry-picking.
> That tooling is something that is perhaps best tried on a release branch
>
Am 24.01.2019 um 10:39 schrieb Volker Hilsheimer:
>> On 24 Jan 2019, at 09:22, Jaroslaw Kobus wrote:
"All(**) changes would go to dev. From which they would be automatically
cherry-picked by a bot to other branches. The decision to which branch
cherry-
pick, would be taken
Hi everybody,
the Qt project is now registered in oss-fuzz's list of projects:
https://github.com/google/oss-fuzz/tree/master/projects
What I have so far:
- fuzzing Qt with libFuzzer locally
- registered Qt project for oss-fuzz
What I don't have so far:
- setting up build/run on Google's
Am 25.10.2018 um 19:39 schrieb André Pönitz:
> On Thu, Oct 25, 2018 at 09:51:00AM +0200, Volker Krause via Development wrote:
>> We do have a Code of Conduct at KDE for about 10 years now, and this hasn't
>> led to abuse of power, suppression of free speech, racism against white
>> people
>> or
Am 25.10.2018 um 09:58 schrieb Lars Knoll:
> And btw, we have had a clear majority in favour of adding a CoC at the
> Contributor Summit, and explicitly agreed that a group of people will work on
> creating it. I’m happy we now have a first version, that we can use as a
> basis for further
Hi,
is there a bugreport about this, already?
Best Regards,
Robert
Am 13.09.2018 um 11:21 schrieb Nils Jeisecke via Development:
> Hi,
>
> using the Jira login form does not work but the "Login" button (on top
> right) does.
>
> Nils
>
> Am 13.09.2018 um 11:15 hat Nils Jeisecke via
18 matches
Mail list logo
