I see submitted patches closing in on 1 month old without any declines or other reasons they are not moving up the chain.
Is the "project" awaiting someone to take over Mr. Kucia's role, and that is the reason things move overly slow?
Sveinar
On Fri, 18 Oct 2019 at 12:11, Sveinar Søpler cybermax@dexter.no wrote:
I see submitted patches closing in on 1 month old without any declines or other reasons they are not moving up the chain.
I'm not entirely sure which patches you're referring to. The oldest ones I still have in my inbox are from October 2. Granted, that's a while ago, but I don't recognise your characterisation.
Is the "project" awaiting someone to take over Mr. Kucia's role, and that is the reason things move overly slow?
We just had a conference. And yes, Józef did an incredible amount of work—certainly not all of it visible on the mailing list—which now has to be taken care of by others. "People" complaining about it on the mailing list doesn't make it better.
Sorry for creating noise.
I (or my mailserver) must have missed something when it comes to the two patches:
Subject: [PATCH] vkd3d: Allow the source to be concurrently rewritten during descriptor copy. Date: Fri, 20 Sep 2019 21:27:31 +1000
+ Subject: [PATCH v4 2/2] vkd3d: Don't allow concurrent writes to descriptors. Date: Wed, 18 Sep 2019 15:58:18 -0500
They might have been rejected or resubmitted with some changes, and i missed that.
Keep up the good work :)
Sveinar
----- On Oct 18, 2019, at 2:37 PM, Henri Verbeet hverbeet@gmail.com wrote:
On Fri, 18 Oct 2019 at 12:11, Sveinar Søpler cybermax@dexter.no wrote:
I see submitted patches closing in on 1 month old without any declines or other reasons they are not moving up the chain.
I'm not entirely sure which patches you're referring to. The oldest ones I still have in my inbox are from October 2. Granted, that's a while ago, but I don't recognise your characterisation.
Is the "project" awaiting someone to take over Mr. Kucia's role, and that is the reason things move overly slow?
We just had a conference. And yes, Józef did an incredible amount of work—certainly not all of it visible on the mailing list—which now has to be taken care of by others. "People" complaining about it on the mailing list doesn't make it better.
Hi Sveinar,
On Fri, 18 Oct 2019 at 23:10, Sveinar Søpler cybermax@dexter.no wrote:
Sorry for creating noise.
I (or my mailserver) must have missed something when it comes to the two patches:
Subject: [PATCH] vkd3d: Allow the source to be concurrently rewritten during descriptor copy. Date: Fri, 20 Sep 2019 21:27:31 +1000
Subject: [PATCH v4 2/2] vkd3d: Don't allow concurrent writes to descriptors. Date: Wed, 18 Sep 2019 15:58:18 -0500
They might have been rejected or resubmitted with some changes, and i missed that.
Both were attempts to address the same issue. The version that eventually made it in is commit 8e6f5ddd24158c7402b5fe28426083539eb7f617. That does look fairly different from the initial patch, so in that sense it's not unusual that someone would miss the connection between those unless they're familiar with the code in question.
Henri
----- On Oct 21, 2019, at 3:12 PM, Henri Verbeet hverbeet@gmail.com wrote:
Both were attempts to address the same issue. The version that eventually made it in is commit 8e6f5ddd24158c7402b5fe28426083539eb7f617. That does look fairly different from the initial patch, so in that sense it's not unusual that someone would miss the connection between those unless they're familiar with the code in question.
Henri
Ah, that explains it.. cos i did not make that connection.
Thank you for clearing that up :)
Sveinar
-
Henri Verbeet -
Sveinar Søpler