On Fri, 17 Feb 2012, Junio C Hamano wrote: > But after trying to write a reroll myself, I have to wonder what would > happen if you have two branches pointing at the same commit as the one at > HEAD. Why isn't the use of current_head class controlled by comparison > between the name of the ref and the output from "symbolic-ref HEAD"? If there is more than one branch that points to HEAD commit, they all will be highlighted. Using "git symbolic-ref HEAD", or just reading '.git/HEAD' file or symlink is on my todo list. This will make gitweb highlight current branch correctly even if there is more than one branch that point to the same HEAD commit, and make it possible to support "detached HEAD" (which I think is not supported at all now). Anyway the test is here to stay... :-) > -- >8 -- > From: Jakub Narebski <jnareb@xxxxxxxxx> > Date: Wed, 15 Feb 2012 16:36:41 +0100 > Subject: [PATCH] gitweb: Fix "heads" view when there is no current branch > > In a repository whose HEAD points to an unborn branch with no commits, > "heads" view and "summary" view (which shows what is shown in "heads" > view) compared the object names of commits at the tip of branches with the > output from "git rev-parse HEAD", which caused comparison of a string with > undef and resulted in a warning in the server log. > > This can happen if non-bare repository (with default 'master' branch) > is updated not via committing but by other means like push to it, or > Gerrit. It can happen also just after running "git checkout --orphan > <new branch>" but before creating any new commit on this branch. > > Rewrite the comparison so that it also works when $head points at nothing; > in such a case, no branch can be "the current branch", add a test for it. > > While at it rename local variable $head to $head_at, as it points to > current commit rather than current branch name (HEAD contents). > > Reported-by: Rajesh Boyapati > Signed-off-by: Jakub Narebski <jnareb@xxxxxxxxx> > Signed-off-by: Junio C Hamano <gitster@xxxxxxxxx> > --- Thanks! -- Jakub Narebski Poland -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html