All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: Christoph Egger <Christoph.Egger@amd.com>, xen-devel@lists.xensource.com
Subject: Re: [PATCH] xen-unstable: 3.0-unstable or 3.1-unstable?
Date: Fri, 17 Aug 2007 15:04:22 +0100	[thread overview]
Message-ID: <C2EB6976.14559%keir@xensource.com> (raw)
In-Reply-To: <200708171455.42352.Christoph.Egger@amd.com>

Yes, 3.0-unstable makes no sense. It should probably be 3.2-unstable, as
these are unstable bits that will be part of the stable 3.2 release. 3.1 is
already out the door.

 -- Keir

On 17/8/07 13:55, "Christoph Egger" <Christoph.Egger@amd.com> wrote:

> 
> When I build xen-unstable, I see this line:
> 
> tools/figlet/figlet -d tools/figlet Xen 3.0-unstable >>
> include/xen/compile.h.new
> 
> Is xen-unstable  3.0-unstable or is this 3.1-unstable?
> 
> In the latter case, the patch below should be applied.
> 
> 
> diff -r 256160ff19b7 xen/Makefile
> --- a/xen/Makefile      Thu Aug 16 13:27:59 2007 +0100
> +++ b/xen/Makefile      Fri Aug 17 14:51:33 2007 +0200
> @@ -1,7 +1,7 @@
>  # This is the correct place to edit the build version.
>  # All other places this is stored (eg. compile.h) should be autogenerated.
>  export XEN_VERSION       = 3
> -export XEN_SUBVERSION    = 0
> +export XEN_SUBVERSION    = 1
>  export XEN_EXTRAVERSION ?= -unstable$(XEN_VENDORVERSION)
>  export XEN_FULLVERSION   = $(XEN_VERSION).
> $(XEN_SUBVERSION)$(XEN_EXTRAVERSION)
>  -include xen-version
> 

      reply	other threads:[~2007-08-17 14:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-17 12:55 [PATCH] xen-unstable: 3.0-unstable or 3.1-unstable? Christoph Egger
2007-08-17 14:04 ` Keir Fraser [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=C2EB6976.14559%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=Christoph.Egger@amd.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.