1. 22 9月, 2018 21 次提交
  2. 18 9月, 2018 1 次提交
  3. 11 9月, 2018 4 次提交
    • J
      Git 2.19 · 1d4361b0
      Junio C Hamano 提交于
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      1d4361b0
    • J
      Merge tag 'l10n-2.19.0-rnd2' of git://github.com/git-l10n/git-po · 46d9a284
      Junio C Hamano 提交于
      l10n for Git 2.19.0 round 2
      
      * tag 'l10n-2.19.0-rnd2' of git://github.com/git-l10n/git-po:
        l10n: zh_CN: for git v2.19.0 l10n round 1 to 2
        l10n: bg.po: Updated Bulgarian translation (3958t)
        l10n: vi.po(3958t): updated Vietnamese translation v2.19.0 round 2
        l10n: es.po v2.19.0 round 2
        l10n: fr.po v2.19.0 rnd 2
        l10n: fr.po v2.19.0 rnd 1
        l10n: fr: fix a message seen in git bisect
        l10n: sv.po: Update Swedish translation (3958t0f0u)
        l10n: git.pot: v2.19.0 round 2 (3 new, 5 removed)
        l10n: ru.po: update Russian translation
        l10n: git.pot: v2.19.0 round 1 (382 new, 30 removed)
        l10n: de.po: translate 108 new messages
        l10n: zh_CN: review for git 2.18.0
        l10n: sv.po: Update Swedish translation(3608t0f0u)
      46d9a284
    • J
      Merge branch 'jn/submodule-core-worktree-revert' · f38a45b9
      Junio C Hamano 提交于
      * jn/submodule-core-worktree-revert:
        Revert "Merge branch 'sb/submodule-core-worktree'"
      f38a45b9
    • J
      Merge branch 'mk/http-backend-content-length' · fe468eff
      Junio C Hamano 提交于
      The earlier attempt barfed when given a CONTENT_LENGTH that is
      set to an empty string.  RFC 3875 is fairly clear that in this
      case we should not read any message body, but we've been reading
      through to the EOF in previous versions (which did not even pay
      attention to the environment variable), so keep that behaviour for
      now in this late update.
      
      * mk/http-backend-content-length:
        http-backend: allow empty CONTENT_LENGTH
      fe468eff
  4. 09 9月, 2018 3 次提交
  5. 08 9月, 2018 2 次提交
    • J
      Revert "Merge branch 'sb/submodule-core-worktree'" · f178c13f
      Jonathan Nieder 提交于
      This reverts commit 7e25437d, reversing
      changes made to 00624d60.
      
      v2.19.0-rc0~165^2~1 (submodule: ensure core.worktree is set after
      update, 2018-06-18) assumes an "absorbed" submodule layout, where the
      submodule's Git directory is in the superproject's .git/modules/
      directory and .git in the submodule worktree is a .git file pointing
      there.  In particular, it uses $GIT_DIR/modules/$name to find the
      submodule to find out whether it already has core.worktree set, and it
      uses connect_work_tree_and_git_dir if not, resulting in
      
      	fatal: could not open sub/.git for writing
      
      The context behind that patch: v2.19.0-rc0~165^2~2 (submodule: unset
      core.worktree if no working tree is present, 2018-06-12) unsets
      core.worktree when running commands like "git checkout
      --recurse-submodules" to switch to a branch without the submodule.  If
      a user then uses "git checkout --no-recurse-submodules" to switch back
      to a branch with the submodule and runs "git submodule update", this
      patch is needed to ensure that commands using the submodule directly
      are aware of the path to the worktree.
      
      It is late in the release cycle, so revert the whole 3-patch series.
      We can try again later for 2.20.
      Reported-by: NAllan Sandfeld Jensen <allan.jensen@qt.io>
      Helped-by: NStefan Beller <sbeller@google.com>
      Signed-off-by: NJonathan Nieder <jrnieder@gmail.com>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      f178c13f
    • M
      http-backend: allow empty CONTENT_LENGTH · 574c513e
      Max Kirillov 提交于
      According to RFC3875, empty environment variable is equivalent to unset,
      and for CONTENT_LENGTH it should mean zero body to read.
      
      However, unset CONTENT_LENGTH is also used for chunked encoding to indicate
      reading until EOF. At least, the test "large fetch-pack requests can be split
      across POSTs" from t5551 starts faliing, if unset or empty CONTENT_LENGTH is
      treated as zero length body. So keep the existing behavior as much as possible.
      
      Add a test for the case.
      Reported-By: NJelmer Vernooij <jelmer@jelmer.uk>
      Signed-off-by: NMax Kirillov <max@max630.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      574c513e
  6. 07 9月, 2018 1 次提交
  7. 06 9月, 2018 5 次提交
  8. 05 9月, 2018 3 次提交