From: Frank Li <lznuaa@gmail.com>
To: git@vger.kernel.org, msysgit@googlegroups.com,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Frank Li <lznuaa@gmail.com>
Subject: Re: [PATCH v2] Fix symlink __stdcall problem at MSVC
Date: Fri, 21 Aug 2009 10:57:10 +0800 [thread overview]
Message-ID: <1976ea660908201957l76ebf555wbbbda0dbfb8cbdd7@mail.gmail.com> (raw)
In-Reply-To: <1250778072-4324-1-git-send-email-lznuaa@gmail.com>
>
> int symlink(const char *oldpath, const char *newpath)
> {
> - typedef BOOL WINAPI (*symlink_fn)(const char*, const char*, DWORD);
> + typedef BOOL (WINAPI *symlink_fn)(const char*, const char*, DWORD);
> static symlink_fn create_symbolic_link = NULL;
> if (!create_symbolic_link) {
> create_symbolic_link = (symlink_fn) GetProcAddress(
> --
> 1.6.4.msysgit.0
>
This is new patch for latest devel branch mingw.c.
prev parent reply other threads:[~2009-08-21 2:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 14:21 [PATCH v2] Fix symlink __stdcall problem at MSVC Frank Li
2009-08-21 2:42 ` Frank Li
2009-08-21 2:57 ` Frank Li [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1976ea660908201957l76ebf555wbbbda0dbfb8cbdd7@mail.gmail.com \
--to=lznuaa@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=msysgit@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).