1. 22 7月, 2013 3 次提交
  2. 20 7月, 2013 22 次提交
  3. 16 7月, 2013 7 次提交
    • J
      Git 1.8.3.3 · 5addd1c7
      Junio C Hamano 提交于
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      5addd1c7
    • J
      Merge branch 'tr/maint-apply-non-git-patch-parsefix' into maint · 90360c71
      Junio C Hamano 提交于
      "git apply" parsed patches that add new files, generated by programs
      other than Git, incorrectly.  This is an old breakage in v1.7.11.
      
      * tr/maint-apply-non-git-patch-parsefix:
        apply: carefully strdup a possibly-NULL name
      90360c71
    • J
      Merge branch 'bc/http-keep-memory-given-to-curl' into maint · 29b2f056
      Junio C Hamano 提交于
      Older cURL wanted piece of memory we call it with to be stable, but
      we updated the auth material after handing it to a call.
      
      * bc/http-keep-memory-given-to-curl:
        http.c: don't rewrite the user:passwd string multiple times
      29b2f056
    • J
      Merge branch 'jk/pull-into-dirty-unborn' into maint · d2db8f78
      Junio C Hamano 提交于
      "git pull" into nothing trashed "local changes" that were in the
      index.
      
      * jk/pull-into-dirty-unborn:
        pull: merge into unborn by fast-forwarding from empty tree
        pull: update unborn branch tip after index
      d2db8f78
    • J
      Merge branch 'fg/submodule-non-ascii-path' into maint · 1f101bf6
      Junio C Hamano 提交于
      Many "git submodule" operations did not work on a submodule at a
      path whose name is not in ASCII.
      
      * fg/submodule-non-ascii-path:
        t7400: test of UTF-8 submodule names pass under Mac OS
        handle multibyte characters in name
      1f101bf6
    • J
      Merge branch 'fc/sequencer-plug-leak' into maint · 1b790212
      Junio C Hamano 提交于
      "cherry-pick" had a small leak in its error codepath.
      
      * fc/sequencer-plug-leak:
        sequencer: avoid leaking message buffer when refusing to create an empty commit
        sequencer: remove useless indentation
      1b790212
    • J
      Merge branch 'mt/send-email-cc-match-fix' into maint · 8ca36db0
      Junio C Hamano 提交于
      Logic used by git-send-email to suppress cc mishandled names like "A
      U. Thor" <author@example.xz>, where the human readable part needs to
      be quoted (the user input may not have the double quotes around the
      name, and comparison was done between quoted and unquoted strings).
      It also mishandled names that need RFC2047 quoting.
      
      * mt/send-email-cc-match-fix:
        send-email: sanitize author when writing From line
        send-email: add test for duplicate utf8 name
        test-send-email: test for pre-sanitized self name
        t/send-email: test suppress-cc=self with non-ascii
        t/send-email: add test with quoted sender
        send-email: make --suppress-cc=self sanitize input
        t/send-email: test suppress-cc=self on cccmd
        send-email: fix suppress-cc=self on cccmd
        t/send-email.sh: add test for suppress-cc=self
      8ca36db0
  4. 09 7月, 2013 2 次提交
  5. 08 7月, 2013 2 次提交
    • R
      3087b615
    • M
      lockfile: fix buffer overflow in path handling · 2fbd4f92
      Michael Haggerty 提交于
      The path of the file to be locked is held in lock_file::filename,
      which is a fixed-length buffer of length PATH_MAX.  This buffer is
      also (temporarily) used to hold the path of the lock file, which is
      the path of the file being locked plus ".lock".  Because of this, the
      path of the file being locked must be less than (PATH_MAX - 5)
      characters long (5 chars are needed for ".lock" and one character for
      the NUL terminator).
      
      On entry into lock_file(), the path length was only verified to be
      less than PATH_MAX characters, not less than (PATH_MAX - 5)
      characters.
      
      When and if resolve_symlink() is called, then that function is
      correctly told to treat the buffer as (PATH_MAX - 5) characters long.
      This part is correct.  However:
      
      * If LOCK_NODEREF was specified, then resolve_symlink() is never
        called.
      
      * If resolve_symlink() is called but the path is not a symlink, then
        the length check is never applied.
      
      So it is possible for a path with length (PATH_MAX - 5 <= len <
      PATH_MAX) to make it through the checks.  When ".lock" is strcat()ted
      to such a path, the lock_file::filename buffer is overflowed.
      
      Fix the problem by adding a check when entering lock_file() that the
      original path is less than (PATH_MAX - 5) characters.
      
      [jc: with independent development by Peff]
      Signed-off-by: NMichael Haggerty <mhagger@alum.mit.edu>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      2fbd4f92
  6. 06 7月, 2013 1 次提交
  7. 04 7月, 2013 3 次提交