[PATCH] oleaut32: Cut off only non-empty \[0-9]+$ resource-id in RegisterTypeLib.
Puetz Kevin A
PuetzKevinA at JohnDeere.com
Thu Jul 16 14:42:59 CDT 2020
Thanks. I take it you prefer commit messages to be briefer and worded for "how it works now", with less discussion of "what was wrong with the previous behavior". Or at least move that explanatory under the --- separator that ends the git commit message. I'll try and follow that for the rest of the submissions I'm preparing...
Do I need to do something to retract my original patch from the queue at https://source.winehq.org/patches/ (it isn't showing as Superseded like I usually see when there is a v2 patch)? If so, how do I do that? https://wiki.winehq.org/Submitting_Patches doesn't seem to say...
> -----Original Message-----
> From: wine-devel <wine-devel-bounces at winehq.org> On Behalf Of Jacek
> Sent: Thursday, July 16, 2020 2:06 PM
> To: wine-devel <wine-devel at winehq.org>
> Subject: [PATCH] oleaut32: Cut off only non-empty \[0-9]+$ resource-id in
> From: Puetz Kevin A <PuetzKevinA at JohnDeere.com>
> Check if szFullPath ended with '\\' (was explicitly a directory).
> Signed-off-by: Kevin Puetz <PuetzKevinA at JohnDeere.com>
> Signed-off-by: Jacek Caban <jacek at codeweavers.com>
> dlls/oleaut32/typelib.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
More information about the wine-devel