Background: The current version of Windows git in depot_tools is much slower on some common operations, like 'stat' and 'fetch', than git on other platforms. We've built a version with some custom patches to try to address the worst of these performance issues. Our testing shows that it is now 2-4 times faster on those operations, but we'd like to get more feedback before making it the default version in depot_tools.Please try this new build and let us know if there are any problems. If you were disappointed with previous git performance, let us know if this version addresses your concerns.You can install by running the following at a Windows command prompt:set DEPOT_TOOLS_GIT_1825=1
gclientOnce installed, 'git --version' should report:git version 1.8.5.2.msysgit.0.1.g01cc1f2If you would like to go back to the default version of git:set DEPOT_TOOLS_GIT_1825=0rd /s /q git-1.8.5.2.chromium.1_bin git-1.8.0_bingclientThanks,Michael, on behalf of chrome-infrastructure-team
Hi,
On Fri, Feb 7, 2014 at 2:22 PM, Michael Moss <mm...@chromium.org> wrote:
Background: The current version of Windows git in depot_tools is much slower on some common operations, like 'stat' and 'fetch', than git on other platforms. We've built a version with some custom patches to try to address the worst of these performance issues. Our testing shows that it is now 2-4 times faster on those operations, but we'd like to get more feedback before making it the default version in depot_tools.Please try this new build and let us know if there are any problems. If you were disappointed with previous git performance, let us know if this version addresses your concerns.
You can install by running the following at a Windows command prompt:
set DEPOT_TOOLS_GIT_1852=1
If I'm not mistaken, DEPOT_TOOLS_GIT_1852, not 1825.
gclientOnce installed, 'git --version' should report:git version 1.8.5.2.msysgit.0.1.g01cc1f2If you would like to go back to the default version of git:
set DEPOT_TOOLS_GIT_1852=0
rd /s /q git-1.8.5.2.chromium.1_bin git-1.8.0_bingclientThanks,Michael, on behalf of chrome-infrastructure-team
--
Takayoshi Kochi
--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
That was intentionally changed to enforce the Chromium policy, and to fix specific problems caused by not having it set properly (e.g. messed up checkouts on buildbots). If you have it set the way you want it in your personal preferences (git config --global or --local), does that not take precedence?FWIW, the previous git also had a hardcoded autocrlf config, it was just set to a different value (probably the one you wanted, so you didn't notice).
/Daniel
Good question, I'm not sure if the setting persists into submodules.
Either way though, I think that long-term gitattributes should be where we head. It makes the setup flow simpler for new developers, allows us to clean up confusing documentation about how to configure git, and makes incorporating new changes downstream simpler.
On Feb 27, 2014 7:39 AM, "Daniel Bratell" <bra...@opera.com> wrote:
>
> On Wed, 26 Feb 2014 17:09:29 +0100, Daniel Bratell <bra...@opera.com> wrote:
>
>> Talking about git performance (going to diverge the thread a bit), what openssl version does the bundled git use on Windows? I've heard (though my search mojo has just left me) that it can help performance to include the right (TM) version of the ssl/crypto libs.
>
>
> OpenSSH not OpenSSL. We had some really good performance results with replacing OpenSSH 4.x in msysgit with OpenSSH 5.2 (copied from an rsync package) half a year ago. People reported up to 10x higher download speeds.
Yes, we made the same observation in the field. However, we don't use ssh transport for any of our repos.
Stefan
Hi all,As of today, git on windows uses a different colour scheme for the git branch command. Its dark blue on black, see attached screenshot, which is not easily readable.
I looked through the git config docs about colours (https://www.kernel.org/pub/software/scm/git/docs/git-config.html), but I did not find a slot for the "upstream branch". I see only slots for "local", "remote", "current", and "plain", none of which fixed this. Does someone know what slot to use?