Skip to content

History / FAQ

Revisions

  • Mention that 2.30.0(2) fixes a vulnerability

    @dscho dscho committed Jan 14, 2021
    83ae4ef

  • Fix whitespace issues Signed-off-by: Johannes Schindelin <[email protected]>

    @dscho dscho committed Dec 19, 2020
    ca955c8

  • Mention that v2.29.2(3) also is one of those versions with critical security fixes

    @dscho dscho committed Dec 8, 2020
    34747f2

  • Mention that Git for Windows older than v2.29.2(2) is vulnerable (due to a Git LFS bug)

    @dscho dscho committed Nov 5, 2020
    714cb33

  • Use links referring to the default branch in a generic way Signed-off-by: Johannes Schindelin <[email protected]>

    @dscho dscho committed Jun 17, 2020
    b2f4a75

  • use https

    @vszakats vszakats committed May 3, 2020
    e526747

  • The latest vulnerabilities were fixed in v2.26.1

    @dscho dscho committed Apr 15, 2020
    3c1c674

  • Recommend updating to v2.24.1(2)

    @dscho dscho committed Dec 10, 2019
    b79c426

  • Fix capitalization

    @elieux elieux committed Nov 9, 2019
    b222d3c

  • Rephrase the sentence about versions that fixed bugs, to avoid confusion whether those versions actually introduced bugs rather than fixing them

    @dscho dscho committed Sep 13, 2019
    969aae5

  • Added large file size issue

    Philip Oakley committed Apr 6, 2019
    d9438cd

  • Add Microsoft Docs reference about TFS.

    @KexyBiscuit KexyBiscuit committed Feb 25, 2019
    0f6a1ea

  • robmen/gitsetup#1 is closed, add new link to msi related files.

    @KexyBiscuit KexyBiscuit committed Feb 22, 2019
    48c2ba6

  • Revert changes to 36d6186.

    @KexyBiscuit KexyBiscuit committed Feb 22, 2019
    1cf8a02

  • Just nod if you can hear me.

    @MrGentry MrGentry committed Feb 17, 2019
    87bcb85

  • Destroyed FAQ (markdown)

    @lwtlp987 lwtlp987 committed Feb 11, 2019
    a9a42c3

  • List the Snapshot build location

    Philip Oakley committed Nov 13, 2018
    36d6186

  • make release notes look like a web link

    Philip Oakley committed Oct 8, 2018
    3a442ad

  • Mention that Git for Windows older than v2.17.1(2) is not safe.

    @dscho dscho committed Jun 20, 2018
    85fa0c1

  • Add some tips how to deal with build errors.

    @telezhnaya telezhnaya committed May 7, 2018
    23bdd32

  • Describe the release cadence of Git for Windows

    @dscho dscho committed Apr 29, 2018
    313a02a

  • Use the new homepage consistently We now use the domain gitforwindows.org, which is much easier to remember and quicker to type. Signed-off-by: Johannes Schindelin <[email protected]>

    @dscho dscho committed Feb 12, 2018
    9786dc0

  • Mention that v2.14.1 fixed a critical security issue

    @dscho dscho committed Aug 15, 2017
    be734de

  • Capture the learning point from issue 1000

    Philip Oakley committed May 21, 2017
    ce8009d

  • FAQ (licenses): add original link It would make more sense to auto-update it, but that would require somebody to put in the effort... Signed-off-by: Johannes Schindelin <[email protected]>

    @dscho dscho committed May 11, 2017
    381142f

  • FAQ (licenses): let Markdown renderer justify the paragraphs Signed-off-by: Johannes Schindelin <[email protected]>

    @dscho dscho committed May 11, 2017
    ab38a6f

  • FAQ (licenses): remove mstmp We do not ship it anymore... Signed-off-by: Johannes Schindelin <[email protected]>

    @dscho dscho committed May 11, 2017
    402a6bb

  • Added licenses section (from git-for-windows/git/README.md and git-for-windows/build-extra/ReleaseNotes.md) to clarify licensing of Git for Windows. Surrounded Win-Command with Code-Span.

    @Polostor Polostor committed May 10, 2017
    0739907

  • Updated FAQ (markdown)

    Philip Oakley committed Apr 22, 2017
    4cc5d9c

  • extracting 7z/zip files - iss #986

    Philip Oakley committed Dec 9, 2016
    7fb842d