1. 13 11月, 2011 1 次提交
  2. 12 11月, 2011 1 次提交
  3. 11 11月, 2011 3 次提交
    • J
      c444c165
    • J
      Merge 'build-in git-mktree' · 77f143bf
      Junio C Hamano 提交于
      * commit '633e3556': (5835 commits)
        build-in git-mktree
        allow -t abbreviation for --track in git branch
        gitweb: Remove function prototypes (cleanup)
        Documentation: cloning to empty directory is allowed
        Clarify kind of conflict in merge-one-file helper
        git config: clarify --add and --get-color
        archive-tar.c: squelch a type mismatch warning
        Start 1.6.4 development
        Start 1.6.3.1 maintenance series.
        GIT 1.6.3
        t4029: use sh instead of bash
        t4200: convert sed expression which operates on non-text file to perl
        t4200: remove two unnecessary lines
        t/annotate-tests.sh: avoid passing a non-newline terminated file to sed
        t4118: avoid sed invocation on file without terminating newline
        t4118: add missing '&&'
        t8005: use egrep when extended regular expressions are required
        git-clean doc: the command only affects paths under $(cwd)
        improve error message in config.c
        t4018-diff-funcname: add cpp xfuncname pattern to syntax test
        ...
      77f143bf
    • L
      mktree: fix a memory leak in write_tree() · cd9519bd
      Liu Yuan 提交于
      We forget to call strbuf_release to release the buf memory.
      Signed-off-by: NLiu Yuan <tailai.ly@taobao.com>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      cd9519bd
  4. 09 11月, 2011 12 次提交
  5. 08 11月, 2011 3 次提交
  6. 07 11月, 2011 5 次提交
  7. 06 11月, 2011 3 次提交
  8. 05 11月, 2011 1 次提交
    • S
      http: don't always prompt for password · 986bbc08
      Stefan Naewe 提交于
      When a username is already specified at the beginning of any HTTP
      transaction (e.g. "git push https://user@hosting.example.com/project.git"
      or "git ls-remote https://user@hosting.example.com/project.git"), the code
      interactively asks for a password before calling into the libcurl library.
      It is very likely that the reason why user included the username in the
      URL is because the user knows that it would require authentication to
      access the resource. Asking for the password upfront would save one
      roundtrip to get a 401 response, getting the password and then retrying
      the request. This is a reasonable optimization.
      
      HOWEVER.
      
      This is done even when $HOME/.netrc might have a corresponding entry to
      access the site, or the site does not require authentication to access the
      resource after all. But neither condition can be determined until we call
      into libcurl library (we do not read and parse $HOME/.netrc ourselves). In
      these cases, the user is forced to respond to the password prompt, only to
      give a password that is not used in the HTTP transaction. If the password
      is in $HOME/.netrc, an empty input would later let the libcurl layer to
      pick up the password from there, and if the resource does not require
      authentication, any input would be taken and then discarded without
      getting used. It is wasteful to ask this unused information to the end
      user.
      
      Reduce the confusion by not trying to optimize for this case and always
      incur roundtrip penalty. An alternative might be to document this and keep
      this round-trip optimization as-is.
      Signed-off-by: NStefan Naewe <stefan.naewe@gmail.com>
      Helped-by: NJeff King <peff@peff.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      986bbc08
  9. 04 11月, 2011 1 次提交
  10. 03 11月, 2011 2 次提交
  11. 02 11月, 2011 8 次提交