All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: building xen without mercury repository access
Date: Wed, 13 Feb 2008 10:30:14 +0100	[thread overview]
Message-ID: <47B2B8A6.3070502@inria.fr> (raw)
In-Reply-To: <18353.31965.275538.772802@mariner.uk.xensource.com>

Ian Jackson a écrit :
> Keir Fraser writes ("Re: [Xen-devel] building xen without mercury repository access"):
>> In this case I have tagged the current Linux repo tip as 'xen-3.2.0' and we
>> will a roll a tarball of that.
> 
> This is now available here:
>  http://bits.xensource.com/oss-xen/release/3.2.0/linux-2.6.18-xen-3.2.0.tar.gz
> and we should have a link to it from xen.org soon.
Cool. However, as it is actually a 2.6.18.8 kernel, could you please
change archive name and top-level directory name to match its content ?
It would make managing its content a bit easier, thanks.

-- 
Guillaume Rousse
Moyens Informatiques - INRIA Futurs
Tel: 01 69 35 69 62

      parent reply	other threads:[~2008-02-13  9:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 17:54 building xen without mercury repository access Guillaume Rousse
2008-02-05 19:08 ` Keir Fraser
2008-02-06 22:10   ` Guillaume Rousse
2008-02-07  8:18     ` Keir Fraser
2008-02-07  9:17       ` Guillaume Rousse
2008-02-07 10:33         ` Yves-Gaël Chény
2008-02-11 22:32       ` Guillaume Rousse
2008-02-11 22:40         ` Valter Douglas Lisbôa Jr.
2008-02-11 23:10         ` Keir Fraser
2008-02-12 10:27           ` Ian Jackson
2008-02-12 10:43             ` Guillaume Rousse
2008-02-12 10:46               ` Keir Fraser
2008-02-12 11:02                 ` Ian Jackson
2008-02-12 11:25                   ` Maximilian Wilhelm
2008-02-12 11:34                     ` Keir Fraser
2008-02-13  9:30                   ` Guillaume Rousse [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=47B2B8A6.3070502@inria.fr \
    --to=guillaume.rousse@inria.fr \
    --cc=Ian.Jackson@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.