1. 17 Feb, 2009 1 commit
    • Giuseppe Bilotta's avatar
      gitweb: fix wrong base URL when non-root DirectoryIndex · 81d3fe9f
      Giuseppe Bilotta authored
      CGI::url() has some issues when rebuilding the script URL if the script
      is a DirectoryIndex.
      
      One of these issue is the inability to strip PATH_INFO, which is why
      we had to do it ourselves.
      
      Another issue is that the resulting URL cannot be used for the <base>
      tag: it works if we're the DirectoryIndex at the root level, but not
      otherwise.
      
      We fix this by building the proper base URL ourselves, and improve the
      comment about the need to strip PATH_INFO manually while we're at it.
      
      Additionally t/t9500-gitweb-standalone-no-errors.sh had to be modified
      to set SCRIPT_NAME variable (CGI standard states that it MUST be set,
      and now gitweb uses it if PATH_INFO is not empty, as is the case for
      some of tests in t9500).
      Signed-off-by: Giuseppe Bilotta's avatarGiuseppe Bilotta <[email protected]>
      Signed-off-by: Jakub Narębski's avatarJakub Narebski <[email protected]>
      Signed-off-by: default avatarJunio C Hamano <[email protected]>
      81d3fe9f
  2. 16 Feb, 2009 3 commits
  3. 15 Feb, 2009 16 commits
  4. 14 Feb, 2009 5 commits
  5. 13 Feb, 2009 4 commits
  6. 12 Feb, 2009 9 commits
  7. 11 Feb, 2009 2 commits
    • Pat Notz's avatar
      Fix contrib/hooks/post-receive-email for new duplicate branch · e5f5050e
      Pat Notz authored
      In the show_new_revisions function, the original code:
      
        git rev-parse --not --branches | grep -v $(git rev-parse $refname) |
      
      isn't quite right since one can create a new branch and push it
      without any new commits.  In that case, two refs will have the same
      sha1 but both would get filtered by the 'grep'.  In the end, we'll
      show ALL the history which is not what we want.  Instead, we should
      list the branches by name and remove the branch being updated and THEN
      pass that list through rev-parse.
      
      Revised as suggested by Jakub Narebski and Junio C Hamano to use
      git-for-each-ref instead of git-branch.  (Thanks!)
      Signed-off-by: default avatarPat Notz <[email protected]>
      Signed-off-by: default avatarJunio C Hamano <[email protected]>
      e5f5050e
    • Shawn O. Pearce's avatar
      Clear the delta base cache if a pack is rebuilt · fa3a0c94
      Shawn O. Pearce authored
      There is some risk that re-opening a regenerated pack file with
      different offsets could leave stale entries within the delta base
      cache that could be matched up against other objects using the same
      "struct packed_git*" and pack offset.
      
      Throwing away the entire delta base cache in this case is safer,
      as we don't have to worry about a recycled "struct packed_git*"
      matching to the wrong base object, resulting in delta apply
      errors while unpacking an object.
      Suggested-by: default avatarDaniel Barkalow <[email protected]>
      Signed-off-by: default avatarShawn O. Pearce <[email protected]>
      Signed-off-by: default avatarJunio C Hamano <[email protected]>
      fa3a0c94