All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carsten Schiers <carsten@schiers.de>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: AW: New 3.3.2 and 3.4.1 release candidates
Date: Mon, 13 Jul 2009 14:27:43 +0200	[thread overview]
Message-ID: <14533314.31247488063799.JavaMail.root@uhura> (raw)

Keir,

could it be that there is something wrong with Config.mk's QEMU_TAG variable?

I get a:

> + git checkout -b dummy xen-3.4.1-rc7
> fatal: git checkout: updating paths is incompatible with switching branches/forcing
> Did you intend to checkout 'xen-3.4.1-rc7' which can not be resolved as commit?
> make[1]: *** [ioemu-dir-find] Fehler 128
> make[1]: Leaving directory `/usr/src/xen/xen-3.4.1-rc7/tools'
> make: *** [tools/ioemu-dir] Fehler 2

It's still working with tag xen-3.4.1-rc5, so I think it could be that the repo has no
-rc7 tag currently...

BR,
Carsten.

----- Originalnachricht -----
Von: Keir Fraser <keir.fraser@eu.citrix.com>
Gesendet: Mon, 13.7.2009 13:10
An: xen-devel@lists.xensource.com
Betreff: [Xen-devel] New 3.3.2 and 3.4.1 release candidates

Folks,

New RCs are tagged as follows:
http://xenbits.xensource.com/xen-3.3-testing.hg (3.3.2-rc5)
http://xenbits.xensource.com/xen-3.4-testing.hg (3.4.1-rc7)

Please test!

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

             reply	other threads:[~2009-07-13 12:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-13 12:27 Carsten Schiers [this message]
2009-07-13 12:58 ` AW: New 3.3.2 and 3.4.1 release candidates Keir Fraser
2009-07-13 13:11   ` Ian Jackson
2009-07-13 13:26     ` Ian Jackson
2009-07-13 13:41       ` AW: " Carsten Schiers
2009-07-13 13:45         ` Ian Jackson
2009-07-13 14:21           ` Mark Johnson
2009-07-13 14:43             ` Ian Jackson

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=14533314.31247488063799.JavaMail.root@uhura \
    --to=carsten@schiers.de \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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 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.