1. 24 Feb, 2019 1 commit
    • Johannes Schindelin's avatar
      README: adjust for final Azure Pipeline ID · 39ffebd2
      Johannes Schindelin authored
      During the six months of development of the Azure Pipelines support, the
      patches went through quite a few iterations of changes, and to test
      those iterations, a temporary build definition was used.
      
      In the meantime, Azure Pipelines support made it to `master`, and we now
      have a regular Azure Pipeline, installed via the common GitHub App
      workflow. This new pipeline has a different name (git.git instead of
      test-git.git), and a new ID (11 instead of 2).
      
      Let's adjust the badge in our README to reflect that final shape of the
      Azure Pipeline.
      Signed-off-by: Johannes Schindelin's avatarJohannes Schindelin <johannes.schindelin@gmx.de>
      Signed-off-by: default avatarJunio C Hamano <gitster@pobox.com>
      39ffebd2
  2. 23 Feb, 2019 2 commits
  3. 22 Feb, 2019 2 commits
  4. 19 Feb, 2019 8 commits
  5. 15 Feb, 2019 1 commit
    • Johannes Schindelin's avatar
      mingw: safe-guard a bit more against getenv() problems · ca1b4116
      Johannes Schindelin authored
      Running up to v2.21.0, we fixed two bugs that were made prominent by the
      Windows-specific change to retain copies of only the 30 latest getenv()
      calls' returned strings, invalidating any copies of previous getenv()
      calls' return values.
      
      While this really shines a light onto bugs of the form where we hold
      onto getenv()'s return values without copying them, it is also a real
      problem for users.
      
      And even if Jeff King's patches merged via 773e4088 (Merge branch
      'jk/save-getenv-result', 2019-01-29) provide further work on that front,
      we are far from done. Just one example: on Windows, we unset environment
      variables when spawning new processes, which potentially invalidates
      strings that were previously obtained via getenv(), and therefore we
      have to duplicate environment values that are somehow involved in
      spawning new processes (e.g. GIT_MAN_VIEWER in show_man_page()).
      
      We do not have a chance to investigate, let address, all of those issues
      in time for v2.21.0, so let's at least help Windows users by increasing
      the number of getenv() calls' return values that are kept valid. The
      number 64 was determined by looking at the average number of getenv()
      calls per process in the entire test suite run on Windows (which is
      around 40) and then adding a bit for good measure. And it is a power of
      two (which would have hit yesterday's theme perfectly).
      Signed-off-by: Johannes Schindelin's avatarJohannes Schindelin <johannes.schindelin@gmx.de>
      Signed-off-by: default avatarJunio C Hamano <gitster@pobox.com>
      ca1b4116
  6. 14 Feb, 2019 19 commits
  7. 13 Feb, 2019 6 commits
  8. 12 Feb, 2019 1 commit