From: Junio C Hamano <gitster@pobox.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: "Giuseppe Bilotta" <giuseppe.bilotta@gmail.com>, git@vger.kernel.org
Subject: Re: gitweb and remote branches
Date: Thu, 30 Aug 2007 14:07:13 -0700 [thread overview]
Message-ID: <7vbqco91fi.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <200708301016.17552.jnareb@gmail.com> (Jakub Narebski's message of "Thu, 30 Aug 2007 10:16:15 +0200")
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.
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.
next prev parent reply other threads:[~2007-08-30 21:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 22:24 gitweb and remote branches Giuseppe Bilotta
2007-08-27 23:29 ` Jakub Narebski
[not found] ` <cb7bb73a0708280253y7d31f347yb84a40982d59d9d2@mail.gmail.com>
[not found] ` <cb7bb73a0708280453k4315e80ej170238a52e66dcb6@mail.gmail.com>
2007-08-29 22:01 ` Jakub Narebski
2007-08-30 7:18 ` Giuseppe Bilotta
2007-08-30 8:16 ` Jakub Narebski
2007-08-30 9:09 ` Giuseppe Bilotta
2007-08-30 21:07 ` Junio C Hamano [this message]
2007-08-30 23:09 ` Giuseppe Bilotta
2007-08-30 23:53 ` Jakub Narebski
2007-08-30 23:59 ` Giuseppe Bilotta
2007-08-31 2:15 ` Giuseppe Bilotta
2007-08-31 10:54 ` [PATCH 01/14] gitweb: get remotes too when getting heads list Giuseppe Bilotta
2007-08-31 10:55 ` [PATCH 02/14] gitweb: make remote heads in heads list optional Giuseppe Bilotta
2007-08-31 10:55 ` [PATCH 03/14] gitweb: git_get_heads_list now accepts an optional list of refs Giuseppe Bilotta
2007-08-31 10:55 ` [PATCH 04/14] gitweb: separate heads and remotes list in summary view Giuseppe Bilotta
2007-08-31 10:59 ` [PATCH 05/14] gitweb: allow refs passed to git_heads_body to use a name different from the hash name Giuseppe Bilotta
2007-08-31 11:05 ` [PATCH 06/14] gitweb: git_split_heads_body function Giuseppe Bilotta
2007-08-31 11:18 ` [PATCH 07/14] gitweb: use CSS to style split head lists Giuseppe Bilotta
2007-08-31 11:18 ` [PATCH 08/14] gitweb: add 'remotes' action as a synonym for git_heads() Giuseppe Bilotta
2007-08-31 11:18 ` [PATCH 09/14] gitweb: split heads list in head view if appropriate Giuseppe Bilotta
2007-08-31 11:19 ` [PATCH 10/14] gitweb: display HEAD in heads list when detached Giuseppe Bilotta
2007-08-31 11:19 ` [PATCH 11/14] gitweb: git_is_head_detached() function Giuseppe Bilotta
2007-08-31 11:19 ` [PATCH 12/14] gitweb: add HEAD to list of shortlog refs if detached Giuseppe Bilotta
2007-08-31 11:19 ` [PATCH 13/14] gitweb: CSS style and refs mark for detached HEAD Giuseppe Bilotta
2007-08-31 11:19 ` [PATCH 14/14] gitweb: minor whitespace cleanups Giuseppe Bilotta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vbqco91fi.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=giuseppe.bilotta@gmail.com \
--cc=jnareb@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).