Skip to content

Releases: git-for-windows/git-snapshots

Tue, 23 May 2017 13:08:31 +0200

24 Jan 22:06
Compare
Choose a tag to compare
git-gui: fix exception when trying to stage with empty file list

If there is nothing to stage, there is nothing to stage. Let's not try
to, even if the file list contains nothing at all.

This fixes https://github.com/git-for-windows/git/issues/1075

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>

Fri, 19 May 2017 15:11:55 +0200

24 Jan 22:06
Compare
Choose a tag to compare
Merge pull request #1170 from dscho/mingw-kill-process

Handle Ctrl+C in Git Bash nicely

Fri, 19 May 2017 12:34:45 +0200

24 Jan 22:06
Compare
Choose a tag to compare
prerelease-2.13.0.windows.1.4.g2dd3603754

squash! Help debugging with MSys2 by optionally executing bash with s…

Thu, 18 May 2017 21:35:50 +0200

24 Jan 22:06
Compare
Choose a tag to compare
Merge pull request #1165 from asheiduk/config-docu

Align documentation for C:\ProgramData\Git\config

Tue, 9 May 2017 23:43:59 +0200

24 Jan 22:05
Compare
Choose a tag to compare
Merge branch 'coverity-v4-plus-fixup'

Coverity is a tool to analyze code statically, trying to find common (or
not so common) problems before they occur in production.

Coverity offers its services to Open Source software, and just like
upstream Git, Git for Windows applied and was granted the use.

While Coverity reports a lot of false positives due to Git's (ab-)use of
the FLEX_ARRAY feature (where it declares a 0-byte or 1-byte array at the
end of a struct, and then allocates a variable-length data structure
holding a variable-length string at the end, so that the struct as well as
the string can be released with a single free()), there were a few issues
reported that are true positives, and not all of them were resource leaks
in builtins (for which it is considered kind of okay to not release memory
just before exit() is called anyway).

This topic branch tries to address a couple of those issues.

Note: there are a couple more issues left, either because they are tricky
to resolve (in some cases, the custody of occasionally-allocated memory is
very unclear) or because it is unclear whether they are false positives
(due to the hard-to-reason-about nature of the code). It's a start,
though.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>

Fri, 5 May 2017 22:23:19 +0200

24 Jan 22:05
Compare
Choose a tag to compare
fixup! mingw: ensure `getcwd()` reports the correct case

The return value of GetCurrentDirectoryW() upon errors is actually 0, not
negative (it cannot be negative, as DWORD is an *unsigned* data type).

Also, when converting from _wgetcwd(), I forgot to add errno explicitly...

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>

Wed, 26 Apr 2017 21:47:04 +0200

24 Jan 22:05
Compare
Choose a tag to compare
t7800: cleanup cruft left behind by tests

Signed-off-by: David Aguilar <davvid@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>

Wed, 26 Apr 2017 21:27:43 +0200

24 Jan 22:05
Compare
Choose a tag to compare
prerelease-2.12.2.windows.2.799.g9f22cae658

Merge pull request #1152 from jeffhostetler/jeffhostetler/msvc_make_c…

Wed, 26 Apr 2017 18:04:22 +0200

24 Jan 22:05
Compare
Choose a tag to compare
Merge branch 'coverity'

Coverity is a tool to analyze code statically, trying to find common (or
not so common) problems before they occur in production.

Coverity offers its services to Open Source software, and just like
upstream Git, Git for Windows applied and was granted the use.

While Coverity reports a lot of false positives due to Git's (ab-)use of
the FLEX_ARRAY feature (where it declares a 0-byte or 1-byte array at the
end of a struct, and then allocates a variable-length data structure
holding a variable-length string at the end, so that the struct as well as
the string can be released with a single free()), there were a few issues
reported that are true positives, and not all of them were resource leaks
in builtins (for which it is considered kind of okay to not release memory
just before exit() is called anyway).

This topic branch tries to address a couple of those issues.

Note: there are a couple more issues left, either because they are tricky
to resolve (in some cases, the custody of occasionally-allocated memory is
very unclear) or because it is unclear whether they are false positives
(due to the hard-to-reason-about nature of the code). It's a start,
though.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>

Wed, 26 Apr 2017 12:00:24 +0200

24 Jan 21:31
Compare
Choose a tag to compare
prerelease-2.12.2.windows.2.408.g91e25e0ef0

Merge pull request #1149 from jeffhostetler/jeffhostetler/do_write_in…