git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Teemu Likonen <tlikonen@iki.fi>
To: git@vger.kernel.org
Cc: Junio C Hamano <junio@pobox.com>
Subject: Re: [PATCH/RFC] Make "git remote rm <remote>" remove file refs/remotes/<remote>/HEAD
Date: Sat, 8 Mar 2008 08:16:10 +0200	[thread overview]
Message-ID: <200803080816.10811.tlikonen@iki.fi> (raw)
In-Reply-To: <7vlk4uyoln.fsf@gitster.siamese.dyndns.org>

Junio C Hamano kirjoitti:

> Junio C Hamano <gitster@pobox.com> writes:
> > I think "update-ref -d" should remove the ref without dereferencing
> > anyway.  How about not doing your patch at all (you would need to
> > manually remove the symref in "prune" codepath as well), and
> > instead doing this?
> >
> > I do not know how this reacts when the tracked HEAD points at a ref
> > that lexicographically sorts earlier, say branch "A".
>
> And it turns out it does not react very well.  You would want to do
> something like this on top of that one.

This turned out to be much more complicated than just deleting a file. 
Thank you, these patches seem to work (at least from user's point of 
view).

      reply	other threads:[~2008-03-08  6:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05 11:38 error: refs/remotes/origin/HEAD points nowhere! Teemu Likonen
2008-03-05 21:24 ` Junio C Hamano
2008-03-06  7:50   ` Teemu Likonen
2008-03-08 22:40   ` [PATCH] builtin remote rm: remove symbolic refs, too Johannes Schindelin
2008-03-09 10:24     ` Junio C Hamano
2008-03-07 21:02 ` [PATCH/RFC] Make "git remote rm <remote>" remove file refs/remotes/<remote>/HEAD Teemu Likonen
2008-03-07 22:18   ` Teemu Likonen
2008-03-08  1:45   ` Junio C Hamano
2008-03-08  1:46   ` Junio C Hamano
2008-03-08  6:16     ` Teemu Likonen [this message]

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=200803080816.10811.tlikonen@iki.fi \
    --to=tlikonen@iki.fi \
    --cc=git@vger.kernel.org \
    --cc=junio@pobox.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).