git/gitweb, branch v1.5.0-rc3

[PATCH] Rename git-repo-config to git-config.

2007-01-29T00:16:53Z

Signed-off-by: Tom Prince Signed-off-by: Junio C Hamano

gitweb: Fix git_patchset_body not closing

2007-01-10T00:23:39Z

Fix case when git_patchset_body didn't close

, for patchsets with last patch empty. This patch also removes some commented out code in git_patchset_body. Signed-off-by: Jakub Narebski Acked-by: Luben Tuikov Signed-off-by: Junio C Hamano

gitweb: Remove superfluous "|" in "commit" view

2007-01-08T02:06:45Z

Remove superfluous trailing "|" separator from difftree part of "commit" view for new files (created in given commit). Signed-off-by: Jakub Narebski Signed-off-by: Junio C Hamano

gitweb: Fix split patches output (e.g. file to symlink)

2007-01-07T06:53:08Z

Do not replace /dev/null in two-line from-file/to-file diff header for split patches ("split" patch mean more than one patch per one diff-tree raw line) by a/file or b/file link. Split patches differ from pair of deletion/creation patch in git diff header: both a/file and b/file are hyperlinks, in all patches in a split. Signed-off-by: Jakub Narebski Signed-off-by: Junio C Hamano

Revert "gitweb: There can be empty patches (in git_patchset_body)"

2007-01-07T06:52:55Z

This reverts commit 1ebb948f656c03a5bdaab4de1a113b9ffcb98bea, as that patch quieted warning but was not proper solution. The previous commit was. Signed-off-by: Jakub Narebski Signed-off-by: Junio C Hamano

gitweb: Fix errors in git_patchset_body for empty patches

2007-01-07T06:52:54Z

We now do not skip over empty patches in git_patchset_body (where empty means that they consist only of git diff header, and of extended diff header, for example "pure rename" patch). This means that after extended diff header there can be next patch (i.e. /^diff /) or end of patchset, and not necessary patch body (i.e. /^--- /). Signed-off-by: Jakub Narebski Signed-off-by: Junio C Hamano

gitweb: Fix error in "rename to"/"copy to" git diff header output

2007-01-07T06:52:52Z

Fix error in git_patchset_body subroutine, which caused "rename to"/"copy to" line in extended diff header to be displayed incorrectly. While at it, fix align. Signed-off-by: Jakub Narebski Signed-off-by: Junio C Hamano

gitweb: Fix error in git_patchest_body for file creation/deletion patch

2007-01-07T06:52:49Z

$from_id, $to_id variables should be local per PATCH. Fix error in git_patchset_body for file creation (deletion) patches, where instead of /dev/null as from-file (to-file) diff header line, it had link to previous file with current file name. This error occured only if there was another patch before file creation (deletion) patch. Signed-off-by: Jakub Narebski Signed-off-by: Junio C Hamano

Blame "linenr" link jumps to previous state at "orig_lineno"

2007-01-05T07:20:43Z

Blame currently displays the commit id which introduced a block of one or more lines, the line numbers wrt the current listing of the file and the file's line contents. The commit id displayed is hyperlinked to the commit. Currently the linenr links are hyperlinked to the same commit id displayed to the left, which is _no_ different than the block of lines displayed, since it is the _same commit_ that is hyperlinked. And thus clicking on it leads to the same state of the file for that chunk of lines. I.e. data mining is not currently possible with gitweb given a chunk of lines introduced by a commit. This patch makes such data mining possible. The line numbers are now hyperlinked to the parent of the commit id of the block of lines. Furthermore they are linked to the line where that block was introduced. Thus clicking on a linenr link will show you the file's line(s) state prior to the commit id you were viewing. So clicking continually on a linenr link shows you how this line and its line number changed over time, leading to the initial commit where it was first introduced. Signed-off-by: Luben Tuikov Signed-off-by: Junio C Hamano

gitweb: Fix "Use of uninitialized value" warning in git_tags_body

2007-01-05T07:19:09Z

Fix "Use of uninitialized value" warning in git_tags_body generated for lightweight tags of tree and blob object; those don't have age ($tag{'age'}) defined. Signed-off-by: Jakub Narebski Signed-off-by: Junio C Hamano