Hi,
From: "Dangling Pointer"
I searched in code and found instances of #ifdef _MSC_VER in
https://github.com/git/git (original repository, not the fork).
I am coming from github, where I have found many native lib
repositories have two build files, build.sh and build.cmd with
Git is a *nix co
kernel.org
> Subject: Re: FeatureRequest: Build improvements for Windows
> Date: Sun, 26 Jul 2015 12:27:19 +0100
>
> (In-line posting preferred; top-posting deprecated ;-)
> (retain all cc's)
>
>> Hmm, it is already happening, isn't it? There is already a support o
(In-line posting preferred; top-posting deprecated ;-)
(retain all cc's)
Hmm, it is already happening, isn't it? There is already a support of
MSVCR in git's code base. I am referring to replacing that current
support of 'older' MSVCR in favor of the latest one, so to make the
git's code base
gmail.com
>> Date: Sun, 26 Jul 2015 00:15:10 -0700
>> Subject: Re: FeatureRequest: Build improvements for Windows
>> To: danglingpoin...@outlook.com
>> CC: git@vger.kernel.org
>>
>> On Sat, Jul 25, 2015 at 11:23 PM, Dangling Pointer
>> wrote:
>>&g
On Sat, Jul 25, 2015 at 11:23 PM, Dangling Pointer
wrote:
> Hello,
>
> In my understanding, the ratio between the mere consumers of git on Windows
> vs. people who compile git for Windows is 100,000 : 1. If there is a breaking
> change in the workflow of the latter set, who use Visual Studio to
Hello,
In my understanding, the ratio between the mere consumers of git on Windows vs.
people who compile git for Windows is 100,000 : 1. If there is a breaking
change in the workflow of the latter set, who use Visual Studio to build git
from source, I assume that is doable given a good reason
6 matches
Mail list logo
