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

Re: gitweb and remote branches

From
Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Date
Aug 30, 2007, 23:09 UTC
Message-ID
<cb7bb73a0708301609s330f8d6fna3755bff346452ab@mail.gmail.com>
In-Reply-To
<7vbqco91fi.fsf@gitster.siamese.dyndns.org>
On 8/30/07, Junio C Hamano <gitster@pobox.com> wrote:
Show 15 quoted lines
> Jakub Narebski <jnareb@gmail.com> writes:
>
> > That reminds me that gitweb has no support for detached HEAD as of yet,
> > although I don't think we want to encourage detached HEAD in public
> > repo.
>
> That logic is flawed, I am afraid.  If you have been talking
> only about serving public repository via gitweb, then the topic
> of the thread becomes totally moot.  Exposing or even having
> remotes/ in public distribution point repository would be even
> more wrong than using detached HEAD in public repository.  Other
> people who interact with you should not have any business what
> you happened to have fetched from _your_ upstream --- if you
> want to publish them and act as a relay for your downstream,
> then they should be fetched from your branch namespace.

OTOH, having 'origin' exposed, and knowing the 'origin' URL, would open lots of interesting fields of research, such as distributed git mirroring to download large repositories from more than a client etc.

Anyway, making visible remotes an option that defaults to disabled would address both the issue above and the one below:

> But obviously people use gitweb/instaweb as a way to view their
> own live repository, and I think it makes sense to show and
> support remotes/ in such a case.  It also would make sense to
> support detached HEAD there as well.

If I understand correctly, a detached HEAD is simply a checkout in the middle of a branch, and thus not named. So what exactly are we looking for when we talk about supporting a detached HEAD? Would it be enough to display HEAD in the list of heads?

-- 
Giuseppe "Oblomov" Bilotta
Previous: Junio C HamanoNext: Jakub Narebski
Message 8 of 25 in “gitweb and remote branches”
  1. Giuseppe BilottaAug 27, 2007
  2. Jakub NarebskiAug 27, 2007
  3. Jakub NarebskiAug 29, 2007
  4. Giuseppe BilottaAug 30, 2007
  5. Jakub NarebskiAug 30, 2007
  6. Giuseppe BilottaAug 30, 2007
  7. Junio C HamanoAug 30, 2007
  8. Giuseppe BilottaAug 30, 2007
  9. Jakub NarebskiAug 30, 2007
  10. Giuseppe BilottaAug 30, 2007
  11. Giuseppe BilottaAug 31, 2007
  12. 01/14 gitweb: get remotes too when getting heads listGiuseppe Bilotta, Aug 31, 2007
  13. 02/14 gitweb: make remote heads in heads list optionalGiuseppe Bilotta, Aug 31, 2007
  14. 03/14 gitweb: git_get_heads_list now accepts an optional list of refs.Giuseppe Bilotta, Aug 31, 2007
  15. 04/14 gitweb: separate heads and remotes list in summary viewGiuseppe Bilotta, Aug 31, 2007
  16. 05/14 gitweb: allow refs passed to git_heads_body to use a name different from the hash nameGiuseppe Bilotta, Aug 31, 2007
  17. 06/14 gitweb: git_split_heads_body function.Giuseppe Bilotta, Aug 31, 2007
  18. 07/14 gitweb: use CSS to style split head lists.Giuseppe Bilotta, Aug 31, 2007
  19. 08/14 gitweb: add 'remotes' action as a synonym for git_heads()Giuseppe Bilotta, Aug 31, 2007
  20. 09/14 gitweb: split heads list in head view if appropriateGiuseppe Bilotta, Aug 31, 2007
  21. 10/14 gitweb: display HEAD in heads list when detachedGiuseppe Bilotta, Aug 31, 2007
  22. 11/14 gitweb: git_is_head_detached() functionGiuseppe Bilotta, Aug 31, 2007
  23. 12/14 gitweb: add HEAD to list of shortlog refs if detachedGiuseppe Bilotta, Aug 31, 2007
  24. 13/14 gitweb: CSS style and refs mark for detached HEADGiuseppe Bilotta, Aug 31, 2007
  25. 14/14 gitweb: minor whitespace cleanupsGiuseppe Bilotta, Aug 31, 2007

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.