git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Issue with gitweb + tag + branch of the same name from master branch commit

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 21, 2009, 00:19 UTC
Message-ID
<7vmy5um32h.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1250811031.26147.42.camel@haakon2.linux-iscsi.org>
"Nicholas A. Bellinger" <nab@linux-iscsi.org> writes:
Show 6 quoted lines
> 22:33 < warthog9> not use the same name, I think what your doing is fine just the identical naming is whats 
>                   causing the problem
> 22:33 < warthog9> like tag-lio-3.0
> 22:33 < nab> Ahhhhhh
> 22:33 < warthog9> and branch: lio-3.0
> 22:34 < warthog9> since I think somewhere in git it's got two different orders of preference for tag vs. branch

I do not speak for gitweb but we typically favor tags over heads. The only place "branch name" take precedence is where the command expects to see a name of a branch, when it can also take any arbitrary object name, and changes behaviour. I.e. "git checkout X", when X is a branch name, checks out the branch so that the next commit advances the tip of that branch.

Previous: Nicholas A. BellingerNext: Jakub Narebski
Message 2 of 4 in “Issue with gitweb + tag + branch of the same name from master branch commit”
  1. Nicholas A. BellingerAug 20, 2009
  2. Junio C HamanoAug 21, 2009
  3. Jakub NarebskiAug 21, 2009
  4. Nicholas A. BellingerAug 22, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.