Skip to content

标签

标签使您能够将历史中的特定点标记为重要点
  • 2.4.0
  • v2.40.0.windows.1
    1d90ca29 · Merge 'readme' into HEAD ·
    Git for Windows v2.40.0
    
    Changes since Git for Windows v2.39.2 (February 14th 2023)
    
    As announced previously, Git for Windows will drop support for Windows
    7 and for Windows 8 in one of the next versions, following Cygwin's and
    MSYS2's lead (Git for Windows relies on MSYS2 for components such as
    Bash and Perl).
    
    Also following the footsteps of the MSYS2 and Cygwin projects on which
    Git for Windows depends, the 32-bit variant of Git for Windows is
    nearing its end of support.
    
    New Features
    
      * Comes with Git v2.40.0.
      * In the olden Git days, there were "dashed" Git commands (e.g.
        git-commit instead of git commit). These haven't been supported for
        interactive use in a really, really long time. But they still
        worked in Git aliases and hooks ("scripts"). Since Git v1.5.4
        (released on February 2nd, 2008), it was discouraged/deprecated to
        use dashed Git commands even in scripts. As of this version, Git
        for Windows no longer supports these dashed commands.
      * Comes with tig v2.5.8.
      * Comes with Bash v5.2 patchlevel 15.
      * Comes with OpenSSL v1.1.1t.
      * Comes with GNU TLS v3.8.0.
      * Comes with cURL v7.88.1.
      * Comes with libfido2 v1.13.0.
      * Comes with Git Credential Manager v2.0.935.
    
    Bug Fixes
    
      * Some commands mishandled absolute paths near the drive root (e.g.
        scalar unregister C:/foo), which has been fixed.
      * When trying to call Cygwin (or for that matter, MSYS2) programs
        from Git Bash, users would frequently be greeted with cryptic error
        messages about a "cygheap" or even just an even more puzzling exit
        code 127. Many of these calls now succeed, allowing basic
        interactions. While it is still not possible for, say, Cygwin's
        vim.exe to interact with the Git Bash's terminal window, it is now
        possible for Cygwin's zstd.exe in conjuction with Git for Windows'
        tar.exe to handle .tar.zst archives.
    
  • v2.40.0-rc2.windows.1
    7c333214 · Merge 'readme' into HEAD ·
    Git for Windows v2.40.0-rc2
    
    Changes since Git for Windows v2.39.2 (February 14th 2023)
    
    As announced previously, Git for Windows will drop support for Windows
    7 and for Windows 8 in one of the next versions, following Cygwin's and
    MSYS2's lead (Git for Windows relies on MSYS2 for components such as
    Bash and Perl).
    
    Also following the footsteps of the MSYS2 and Cygwin projects on which
    Git for Windows depends, the 32-bit variant of Git for Windows is
    nearing its end of support.
    
    New Features
    
      * Comes with Git v2.40.0-rc2.
      * In the olden Git days, there were "dashed" Git commands (e.g.
        git-commit instead of git commit). These haven't been supported for
        interactive use in a really, really long time. But they still
        worked in Git aliases and hooks ("scripts"). Since Git v1.5.4
        (released on February 2nd, 2008), it was discouraged/deprecated to
        use dashed Git commands even in scripts. As of this version, Git
        for Windows no longer supports these dashed commands.
      * Comes with tig v2.5.8.
      * Comes with Bash v5.2 patchlevel 15.
      * Comes with OpenSSL v1.1.1t.
      * Comes with GNU TLS v3.8.0.
      * Comes with cURL v7.88.1.
      * Comes with libfido2 v1.13.0.
      * Comes with Git Credential Manager v2.0.935.
    
    Bug Fixes
    
      * Some commands mishandled absolute paths near the drive root (e.g.
        scalar unregister C:/foo), which has been fixed.
      * When trying to call Cygwin (or for that matter, MSYS2) programs
        from Git Bash, users would frequently be greeted with cryptic error
        messages about a "cygheap" or even just an even more puzzling exit
        code 127. Many of these calls now succeed, allowing basic
        interactions. While it is still not possible for, say, Cygwin's
        vim.exe to interact with the Git Bash's terminal window, it is now
        possible for Cygwin's zstd.exe in conjuction with Git for Windows'
        tar.exe to handle .tar.zst archives.
    
  • v2.40.0-rc1.windows.1
    c8edb521 · Merge 'readme' into HEAD ·
    Git for Windows v2.40.0-rc1
    
    Changes since Git for Windows v2.39.2 (February 14th 2023)
    
    As announced previously, Git for Windows will drop support for Windows
    7 and for Windows 8 in one of the next versions, following Cygwin's and
    MSYS2's lead (Git for Windows relies on MSYS2 for components such as
    Bash and Perl).
    
    Also following the footsteps of the MSYS2 and Cygwin projects on which
    Git for Windows depends, the 32-bit variant of Git for Windows is
    nearing its end of support.
    
    New Features
    
      * Comes with Git v2.40.0-rc1.
      * In the olden Git days, there were "dashed" Git commands (e.g.
        git-commit instead of git commit). These haven't been supported for
        interactive use in a really, really long time. But they still
        worked in Git aliases and hooks ("scripts"). Since Git v1.5.4
        (released on February 2nd, 2008), it was discouraged/deprecated to
        use dashed Git commands even in scripts. As of this version, Git
        for Windows no longer supports these dashed commands.
      * Comes with tig v2.5.8.
      * Comes with Bash v5.2 patchlevel 15.
      * Comes with OpenSSL v1.1.1t.
      * Comes with GNU TLS v3.8.0.
      * Comes with cURL v7.88.1.
      * Comes with libfido2 v1.13.0.
      * Comes with Git Credential Manager v2.0.935.
    
    Bug Fixes
    
      * Some commands mishandled absolute paths near the drive root (e.g.
        scalar unregister C:/foo), which has been fixed.
      * When trying to call Cygwin (or for that matter, MSYS2) programs
        from Git Bash, users would frequently be greeted with cryptic error
        messages about a "cygheap" or even just an even more puzzling exit
        code 127. Many of these calls now succeed, allowing basic
        interactions. While it is still not possible for, say, Cygwin's
        vim.exe to interact with the Git Bash's terminal window, it is now
        possible for Cygwin's zstd.exe in conjuction with Git for Windows'
        tar.exe to handle .tar.zst archives.
    
  • v2.40.0-rc0.windows.1
    1c5ccfa9 · Merge 'readme' into HEAD ·
    Git for Windows v2.40.0-rc0
    
    'C:\Windows\system32\drivers\etc\hosts' -> '/etc/hosts'
    'C:\Windows\system32\drivers\etc\protocol' -> '/etc/protocols'
    'C:\Windows\system32\drivers\etc\services' -> '/etc/services'
    'C:\Windows\system32\drivers\etc\networks' -> '/etc/networks'
    
  • v2.39.2.windows.1
    a82fa99b · Merge 'readme' into HEAD ·
    Git for Windows v2.39.2
    
    Creating /dev/shm directory failed.
    POSIX semaphores and POSIX shared memory will not work
    
    Creating /dev/mqueue directory failed.
    POSIX message queues will not work
    
    'C:\Windows\system32\drivers\etc\hosts' -> '/etc/hosts'
    'C:\Windows\system32\drivers\etc\protocol' -> '/etc/protocols'
    'C:\Windows\system32\drivers\etc\services' -> '/etc/services'
    'C:\Windows\system32\drivers\etc\networks' -> '/etc/networks'
    
  • v2.35.7.windows.1
    MinGit for Windows v2.35.7
    
    Changes since Git for Windows v2.35.6 (January 17 2023):
    
    Bug Fixes
    
    * CVE-2023-22490:
    
      Using a specially-crafted repository, Git can be tricked into using
      its local clone optimization even when using a non-local transport.
      Though Git will abort local clones whose source $GIT_DIR/objects
      directory contains symbolic links (c.f., CVE-2022-39253), the objects
      directory itself may still be a symbolic link.
    
      These two may be combined to include arbitrary files based on known
      paths on the victim's filesystem within the malicious repository's
      working copy, allowing for data exfiltration in a similar manner as
      CVE-2022-39253.
    
    * CVE-2023-23946:
    
      By feeding a crafted input to "git apply", a path outside the
      working tree can be overwritten as the user who is running "git
      apply".
    
    * A mismatched type in `attr.c::read_attr_from_index()` which could
      cause Git to errantly reject attributes on Windows and 32-bit Linux
      has been corrected.
    
  • v2.39.1.windows.1
    b03dafd9 · Merge 'readme' into HEAD ·
    Git for Windows v2.39.1
    
    Creating /dev/shm directory failed.
    POSIX semaphores and POSIX shared memory will not work
    
    Creating /dev/mqueue directory failed.
    POSIX message queues will not work
    
    'C:\Windows\system32\drivers\etc\hosts' -> '/etc/hosts'
    'C:\Windows\system32\drivers\etc\protocol' -> '/etc/protocols'
    'C:\Windows\system32\drivers\etc\services' -> '/etc/services'
    'C:\Windows\system32\drivers\etc\networks' -> '/etc/networks'
    
  • v2.35.6.windows.1
    MinGit for Windows v2.35.6
    
    Changes since Git for Windows v2.35.5 (October 13 2022):
    
    Bug Fixes
    
    * CVE-2022-41903:
    
       git log has the ability to display commits using an arbitrary
       format with its --format specifiers. This functionality is also
       exposed to git archive via the export-subst gitattribute.
    
       When processing the padding operators (e.g., %<(, %<|(, %>(,
       %>>(, or %><( ), an integer overflow can occur in
       pretty.c::format_and_pad_commit() where a size_t is improperly
       stored as an int, and then added as an offset to a subsequent
       memcpy() call.
    
       This overflow can be triggered directly by a user running a
       command which invokes the commit formatting machinery (e.g., git
       log --format=...). It may also be triggered indirectly through
       git archive via the export-subst mechanism, which expands format
       specifiers inside of files within the repository during a git
       archive.
    
       This integer overflow can result in arbitrary heap writes, which
       may result in remote code execution.
    
    * CVE-2022-23521:
    
       gitattributes are a mechanism to allow defining attributes for
       paths. These attributes can be defined by adding a `.gitattributes`
       file to the repository, which contains a set of file patterns and
       the attributes that should be set for paths matching this pattern.
    
       When parsing gitattributes, multiple integer overflows can occur
       when there is a huge number of path patterns, a huge number of
       attributes for a single pattern, or when the declared attribute
       names are huge.
    
       These overflows can be triggered via a crafted `.gitattributes` file
       that may be part of the commit history. Git silently splits lines
       longer than 2KB when parsing gitattributes from a file, but not when
       parsing them from the index. Consequentially, the failure mode
       depends on whether the file exists in the working tree, the index or
       both.
    
       This integer overflow can result in arbitrary heap reads and writes,
       which may result in remote code execution.
    
  • v2.39.0.windows.2
    Git for Windows v2.39.0(2)
    
    Creating /dev/shm directory failed.
    POSIX semaphores and POSIX shared memory will not work
    
    Creating /dev/mqueue directory failed.
    POSIX message queues will not work
    
    'C:\Windows\system32\drivers\etc\hosts' -> '/etc/hosts'
    'C:\Windows\system32\drivers\etc\protocol' -> '/etc/protocols'
    'C:\Windows\system32\drivers\etc\services' -> '/etc/services'
    'C:\Windows\system32\drivers\etc\networks' -> '/etc/networks'
    
  • v2.39.0.windows.1
    de9501c6 · Merge 'readme' into HEAD ·
    Git for Windows v2.39.0
    
    Creating /dev/shm directory failed.
    POSIX semaphores and POSIX shared memory will not work
    
    Creating /dev/mqueue directory failed.
    POSIX message queues will not work
    
    'C:\Windows\system32\drivers\etc\hosts' -> '/etc/hosts'
    'C:\Windows\system32\drivers\etc\protocol' -> '/etc/protocols'
    'C:\Windows\system32\drivers\etc\services' -> '/etc/services'
    'C:\Windows\system32\drivers\etc\networks' -> '/etc/networks'
    
  • v2.39.0-rc2.windows.1
    d98e7371 · Merge 'readme' into HEAD ·
    Git for Windows v2.39.0-rc2
    
    Creating /dev/shm directory failed.
    POSIX semaphores and POSIX shared memory will not work
    
    Creating /dev/mqueue directory failed.
    POSIX message queues will not work
    
    'C:\Windows\system32\drivers\etc\hosts' -> '/etc/hosts'
    'C:\Windows\system32\drivers\etc\protocol' -> '/etc/protocols'
    'C:\Windows\system32\drivers\etc\services' -> '/etc/services'
    'C:\Windows\system32\drivers\etc\networks' -> '/etc/networks'
    
  • v2.39.0-rc1.windows.1
    9bd99413 · Merge 'readme' into HEAD ·
    Git for Windows v2.39.0-rc1
    
    Creating /dev/shm directory failed.
    POSIX semaphores and POSIX shared memory will not work
    
    Creating /dev/mqueue directory failed.
    POSIX message queues will not work
    
    'C:\Windows\system32\drivers\etc\hosts' -> '/etc/hosts'
    'C:\Windows\system32\drivers\etc\protocol' -> '/etc/protocols'
    'C:\Windows\system32\drivers\etc\services' -> '/etc/services'
    'C:\Windows\system32\drivers\etc\networks' -> '/etc/networks'
    
  • v2.39.0-rc0.windows.1
    b8a1f167 · Merge 'readme' into HEAD ·
    Git for Windows v2.39.0-rc0
    
    Creating /dev/shm directory failed.
    POSIX semaphores and POSIX shared memory will not work
    
    Creating /dev/mqueue directory failed.
    POSIX message queues will not work
    
    'C:\Windows\system32\drivers\etc\hosts' -> '/etc/hosts'
    'C:\Windows\system32\drivers\etc\protocol' -> '/etc/protocols'
    'C:\Windows\system32\drivers\etc\services' -> '/etc/services'
    'C:\Windows\system32\drivers\etc\networks' -> '/etc/networks'
    
  • v2.35.5.windows.1
    v2.35.5.windows.1
  • v2.38.1.windows.1
    Git for Windows v2.38.1
    
    Creating /dev/shm directory failed.
    POSIX semaphores and POSIX shared memory will not work
    
    Creating /dev/mqueue directory failed.
    POSIX message queues will not work
    
    'C:\Windows\system32\drivers\etc\hosts' -> '/etc/hosts'
    'C:\Windows\system32\drivers\etc\protocol' -> '/etc/protocols'
    'C:\Windows\system32\drivers\etc\services' -> '/etc/services'
    'C:\Windows\system32\drivers\etc\networks' -> '/etc/networks'
    
  • v2.38.0.windows.1
    0355083f · Merge 'readme' into HEAD ·
    Git for Windows v2.38.0
    
    Creating /dev/shm directory failed.
    POSIX semaphores and POSIX shared memory will not work
    
    Creating /dev/mqueue directory failed.
    POSIX message queues will not work
    
    'C:\Windows\system32\drivers\etc\hosts' -> '/etc/hosts'
    'C:\Windows\system32\drivers\etc\protocol' -> '/etc/protocols'
    'C:\Windows\system32\drivers\etc\services' -> '/etc/services'
    'C:\Windows\system32\drivers\etc\networks' -> '/etc/networks'
    
  • v2.38.0-rc2.windows.1
    6f44f232 · Merge 'readme' into HEAD ·
    Git for Windows v2.38.0-rc2
    
    Creating /dev/shm directory failed.
    POSIX semaphores and POSIX shared memory will not work
    
    Creating /dev/mqueue directory failed.
    POSIX message queues will not work
    
    'C:\Windows\system32\drivers\etc\hosts' -> '/etc/hosts'
    'C:\Windows\system32\drivers\etc\protocol' -> '/etc/protocols'
    'C:\Windows\system32\drivers\etc\services' -> '/etc/services'
    'C:\Windows\system32\drivers\etc\networks' -> '/etc/networks'
    
  • v2.38.0-rc1.windows.1
    d4b91089 · Merge 'readme' into HEAD ·
    Git for Windows v2.38.0-rc1
    
    Creating /dev/shm directory failed.
    POSIX semaphores and POSIX shared memory will not work
    
    Creating /dev/mqueue directory failed.
    POSIX message queues will not work
    
    'C:\Windows\system32\drivers\etc\hosts' -> '/etc/hosts'
    'C:\Windows\system32\drivers\etc\protocol' -> '/etc/protocols'
    'C:\Windows\system32\drivers\etc\services' -> '/etc/services'
    'C:\Windows\system32\drivers\etc\networks' -> '/etc/networks'
    
  • v2.38.0-rc0.windows.1
    6b74337f · Merge 'readme' into HEAD ·
    Git for Windows v2.38.0-rc0
    
    Creating /dev/shm directory failed.
    POSIX semaphores and POSIX shared memory will not work
    
    Creating /dev/mqueue directory failed.
    POSIX message queues will not work
    
    'C:\Windows\system32\drivers\etc\hosts' -> '/etc/hosts'
    'C:\Windows\system32\drivers\etc\protocol' -> '/etc/protocols'
    'C:\Windows\system32\drivers\etc\services' -> '/etc/services'
    'C:\Windows\system32\drivers\etc\networks' -> '/etc/networks'