...
From 61bb723f69ea9a9650ef950e4fa31ed63c4de0f9 Mon Sep 17 00:00:00 2001
From: Biswapriyo Nath
Date: Tue, 5 Nov 2019 10:26:30 +0530
Subject: [PATCH] include/wincrypt: update header file
Signed-off-by: Biswapriyo Nath
---
mingw-w64-headers/include/wincrypt.h | 576 +--
在 2019/11/4 18:37, Jacek Caban 写道:
> Signed-off-by: Jacek Caban
> ---
> mingw-w64-headers/include/wincrypt.h | 4
> 1 file changed, 4 insertions(+)
>
>
This patch looks good to me.
--
Best regards,
LH_Mouse
signature.asc
Description: OpenPGP digital signature
There are many changes in this file. Wait for my patch (2-3 hrs).
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
> Could you please elaborate on that? "copy" may mean different things in this
> context.
Your previous statement answered it: "You're free to read it all you
want, APIs are not copyrightable."
___
Mingw-w64-public mailing list
Signed-off-by: Jacek Caban
---
mingw-w64-headers/include/wincrypt.h | 4
1 file changed, 4 insertions(+)
diff --git a/mingw-w64-headers/include/wincrypt.h b/mingw-w64-headers/include/wincrypt.h
index 7425823f..0e84a351 100644
--- a/mingw-w64-headers/include/wincrypt.h
+++
On 02/11/2019 15:46, Biswapriyo Nath wrote:
Thank you for the help. I've sent the patch in Wine devel mailing list. Two
questions:
1. If I want to improve a file which is in wine-import.sh shell script,
should I send patch twice -- one for mingw-w64 and one for wine-devel?
Sending to
