1. 19 10月, 2012 4 次提交
  2. 18 10月, 2012 15 次提交
  3. 17 10月, 2012 6 次提交
  4. 16 10月, 2012 3 次提交
  5. 15 10月, 2012 1 次提交
  6. 14 10月, 2012 2 次提交
  7. 13 10月, 2012 2 次提交
    • J
      Merge branch 'maint' · fc364c76
      Junio C Hamano 提交于
      * maint:
        gitweb.cgi: fix "comitter_tz" typo in feed
      fc364c76
    • J
      http: fix segfault in handle_curl_result · 188923f0
      Jeff King 提交于
      When we create an http active_request_slot, we can set its
      "results" pointer back to local storage. The http code will
      fill in the details of how the request went, and we can
      access those details even after the slot has been cleaned
      up.
      
      Commit 88097030 (http: factor out http error code handling)
      switched us from accessing our local results struct directly
      to accessing it via the "results" pointer of the slot. That
      means we're accessing the slot after it has been marked as
      finished, defeating the whole purpose of keeping the results
      storage separate.
      
      Most of the time this doesn't matter, as finishing the slot
      does not actually clean up the pointer. However, when using
      curl's multi interface with the dumb-http revision walker,
      we might actually start a new request before handing control
      back to the original caller. In that case, we may reuse the
      slot, zeroing its results pointer, and leading the original
      caller to segfault while looking for its results inside the
      slot.
      
      Instead, we need to pass a pointer to our local results
      storage to the handle_curl_result function, rather than
      relying on the pointer in the slot struct. This matches what
      the original code did before the refactoring (which did not
      use a separate function, and therefore just accessed the
      results struct directly).
      Signed-off-by: NJeff King <peff@peff.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      188923f0
  8. 12 10月, 2012 2 次提交
  9. 11 10月, 2012 5 次提交