All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dustin Kirkland <kirkland@canonical.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] QEMU bug tracker on Launchpad
Date: Tue, 23 Jun 2009 12:09:30 -0500	[thread overview]
Message-ID: <1245776970.4506.6.camel@t61p> (raw)
In-Reply-To: <f43fc5580906231002q512ffa2lb10681f8d3baf6f7@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 887 bytes --]

On Tue, 2009-06-23 at 20:02 +0300, Blue Swirl wrote:
> On 6/23/09, Anthony Liguori <aliguori@us.ibm.com> wrote:
> > Dustin Kirkland was kind enough to setup a bug tracker for QEMU on
> > Launchpad.  I would like to make this the official QEMU bug tracker unless
> > there is significant objection.
> 
> The links on code tab do not show which is our tree and there are some
> Ubuntu trees:
> https://code.launchpad.net/qemu
> 
> Can that be fixed?

This 'code' tab does not yet support git.  The trees you're seeing are
bzr.  I don't think Anthony has any intention of using the bzr functions
of Launchpad, and the qemu git tree will remain at
git://git.savannah.nongnu.org/qemu.git.

For convenience, I have setup a periodic sync of the latest git (using
git fast-export | bzr fast-import -).

I'll move the Ubuntu trees elsewhere, sorry for the noise.

:-Dustin

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2009-06-23 17:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23  0:03 QEMU bug tracker on Launchpad Anthony Liguori
2009-06-23  0:03 ` [Qemu-devel] " Anthony Liguori
2009-06-23 17:02 ` Blue Swirl
2009-06-23 17:09   ` Dustin Kirkland [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=1245776970.4506.6.camel@t61p \
    --to=kirkland@canonical.com \
    --cc=aliguori@us.ibm.com \
    --cc=blauwirbel@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.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.