All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: xen-devel@lists.xen.org
Subject: Re: [ANNOUNCE] Switching to qemu-xen.git and qemu-xen-traditional.git
Date: Wed, 21 Oct 2015 17:11:35 +0100	[thread overview]
Message-ID: <1445443895.9563.193.camel@citrix.com> (raw)
In-Reply-To: <1445442757.9563.187.camel@citrix.com>

On Wed, 2015-10-21 at 16:52 +0100, Ian Campbell wrote:
> On Wed, 2015-10-21 at 17:26 +0200, Olaf Hering wrote:
> > On Wed, Oct 21, Ian Campbell wrote:
> > 
> > > http://xenbits.xen.org/gitweb/?p=qemu-xen.git
> > 
> > Is the HEAD warning expected?
> 
> No it is not.

Apparently it actually is, it's a short coming of the git:// protocol that
the client only sees the sha which HEAD points to and has to reverse
engineer which branch it was, which is ambiguous if there are two such
branches (as there is in this repo right now).

Ian J found this which explains things a bit better:

http://stackoverflow.com/questions/13061364/why-git-remote-show-name-display-remote-head-is-ambiguous-may-be-one-of-the

> 
> Both trees contain a file HEAD containing:
>     ref: refs/heads/master
> which is the same as xen.git does.

> I see the same thing as you for the qemu-xen tree, but not for xen.git.


In xen.git staging and master happen to differ right now, so we don't see
this there.

> I shall consult around and see if I can figure out what I'm supposed to do
> here.

a) Nothing, sorry.

Maybe one day a) will be "update git on xenbits", I don't intend to even
investigate that right now, for hopefully obvious reasons...

Ian.

      reply	other threads:[~2015-10-21 16:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 13:16 [ANNOUNCE] Switching to qemu-xen.git and qemu-xen-traditional.git Ian Campbell
2015-10-21 15:07 ` Killed osstest flights (Was: Re: [ANNOUNCE] Switching to qemu-xen.git and qemu-xen-traditional.git) Ian Campbell
2015-10-21 15:26 ` [ANNOUNCE] Switching to qemu-xen.git and qemu-xen-traditional.git Olaf Hering
2015-10-21 15:52   ` Ian Campbell
2015-10-21 16:11     ` Ian Campbell [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=1445443895.9563.193.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=olaf@aepfle.de \
    --cc=xen-devel@lists.xen.org \
    /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.