git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: "Jeff King" <peff@peff.net>,
	"Michael J Gruber" <git@drmicha.warpmail.net>,
	"Marc-André Lureau" <marcandre.lureau@gmail.com>,
	git@vger.kernel.org
Subject: Re: Deleting remote branch pointed by remote HEAD
Date: Wed, 21 Jan 2009 12:42:27 -0800	[thread overview]
Message-ID: <7veiywe6h8.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: alpine.LNX.1.00.0901211237530.19665@iabervon.org

Daniel Barkalow <barkalow@iabervon.org> writes:

> That is, refs/remotes/origin/HEAD is only there to let the user abbreviate 
> the most useful branch of the remote; there's no reason it should reflect 
> the remote's HEAD, except that the remote's HEAD is a good guess if the 
> user hasn't said anything.
>
> I think it might be more appropriate to just care less about a broken 
> symref, explain what's wrong if the user actually tries to use it, and 
> otherwise mostly ignore it.

I agree with you in many of the points in your message.

The user used to be able to say "origin" as a shorthand for "origin/frotz"
by having "remotes/origin/HEAD" locally, and somebody (not necessarily the
user himself) broke this arrangement.  Silently discarding HEAD will lose
the information on which remote branch was the interesting one for the
user.  It may also change the disambiguation rules for "origin" without
telling the user.  Neither is desirable.

The tool needs a better explanation of the situation.  We also want an
easier way to help the user repoint the HEAD to something else, or remove
the dangling HEAD than telling him to use symbolic-ref.

  parent reply	other threads:[~2009-01-21 20:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21 13:02 Deleting remote branch pointed by remote HEAD Marc-André Lureau
2009-01-21 14:33 ` Michael J Gruber
2009-01-21 14:38   ` Marc-André Lureau
2009-01-21 15:24     ` Michael J Gruber
2009-01-21 15:41       ` Marc-André Lureau
2009-01-21 16:19       ` Jeff King
2009-01-21 18:30         ` Daniel Barkalow
2009-01-21 19:09           ` Boyd Stephen Smith Jr.
2009-01-21 19:12           ` Jeff King
2009-01-21 19:14             ` Jeff King
2009-01-21 19:50               ` Daniel Barkalow
2009-01-21 19:53                 ` Jeff King
2009-03-12  9:02                   ` Felipe Contreras
2009-03-12 11:39                     ` Jeff King
2009-03-12 12:47                       ` Felipe Contreras
2009-03-12 12:50                         ` Jeff King
2009-01-21 20:42           ` Junio C Hamano [this message]
2009-01-21 18:31         ` Felipe Contreras
2009-01-21 19:16           ` Jeff King
2009-01-21 19:20             ` Felipe Contreras
2009-01-21 14:41   ` Adeodato Simó
2009-01-21 14:52 ` Sitaram Chamarty
2009-01-21 22:56   ` GUI and detatched HEAD (was Re: Deleting remote branch pointed by remote HEAD) Daniel Barkalow
2009-01-22 14:20     ` Sitaram Chamarty

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=7veiywe6h8.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=barkalow@iabervon.org \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=marcandre.lureau@gmail.com \
    --cc=peff@peff.net \
    /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).