projects / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 83543a2) | patch
gitweb: Fix setting $/ in parse_commit() v1.4.3.2
authorPetr Baudis <pasky@suse.cz>
Tue, 24 Oct 2006 00:39:14 +0000 (02:39 +0200)
committerJunio C Hamano <junkio@cox.net>
Tue, 24 Oct 2006 02:21:05 +0000 (19:21 -0700)
commita153adf683d2b6e22c7e892ed8a161b140156186
treeddd2c5f05bc6ad23ff4512fd706a5984c75ba3actree | snapshot
parent83543a24c316de60b886cd98272fde2bcc99d558commit | diff
gitweb: Fix setting $/ in parse_commit()

If the commit couldn't have been read, $/ wasn't restored to \n properly,
causing random havoc like git_get_ref_list() returning the ref names with
trailing \n.

Aside of potential confusion in the body of git_search(), no other $/
surprises are hopefully hidden in the code.

Signed-off-by: Petr Baudis <pasky@suse.cz>
Signed-off-by: Junio C Hamano <junkio@cox.net>
gitweb/gitweb.perl diff | blob | history
Git—the stupid content tracker