All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Jay Soffian <jaysoffian@gmail.com>, Jeff King <peff@peff.net>,
	git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH 2/3] builtin-remote: teach show to display remote HEAD
Date: Thu, 12 Feb 2009 13:24:48 -0800	[thread overview]
Message-ID: <7vfxijjqlb.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LNX.1.00.0902121519160.19665@iabervon.org> (Daniel Barkalow's message of "Thu, 12 Feb 2009 15:27:13 -0500 (EST)")

Daniel Barkalow <barkalow@iabervon.org> writes:

> I have the vague memory, as well, that there's some way for a transport to 
> report that it actually knows that HEAD is a symref to something in 
> particular, and so git shouldn't guess.

I think you are thinking about:

    http://thread.gmane.org/gmane.comp.version-control.git/102039

  reply	other threads:[~2009-02-12 21:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-11  6:01 [PATCH 0/3] remote HEAD improvements Jay Soffian
2009-02-11  6:01 ` [PATCH 1/3] builtin-remote: move duplicated cleanup code its own function Jay Soffian
2009-02-11  6:01   ` [PATCH 2/3] builtin-remote: teach show to display remote HEAD Jay Soffian
2009-02-11  6:01     ` [PATCH 3/3] builtin-remote: add sethead verb Jay Soffian
2009-02-12  0:26     ` [PATCH 2/3] builtin-remote: teach show to display remote HEAD Jeff King
2009-02-12  1:48       ` Jay Soffian
2009-02-12  1:56         ` Jeff King
2009-02-12 20:27         ` Daniel Barkalow
2009-02-12 21:24           ` Junio C Hamano [this message]
2009-02-12 21:34             ` Daniel Barkalow
2009-02-12 21:37           ` Jay Soffian
2009-02-12 22:55             ` Daniel Barkalow
2009-02-12  0:18   ` [PATCH 1/3] builtin-remote: move duplicated cleanup code its own function Jeff King
2009-02-12  1:44     ` Jay Soffian
2009-02-12  1:50       ` Jeff King
2009-02-12 20:13       ` Daniel Barkalow
2009-02-12  0:17 ` [PATCH 0/3] remote HEAD improvements Jeff King

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=7vfxijjqlb.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=jaysoffian@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.