All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Baruch Even <baruch-6P1Dz+XQpLLYtjvyW6yDsg@public.gmane.org>
Cc: KVM <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Versioning of KVM
Date: Wed, 15 Nov 2006 09:50:47 +0200	[thread overview]
Message-ID: <455AC6D7.4060906@qumranet.com> (raw)
In-Reply-To: <20061115071251.GN28027-xGn4Jn0woyz+OtfAA3OxFg@public.gmane.org>

Baruch Even wrote:
> Avi,
>
> Can you please decide on a normal version number for KVM? I currently
> use 0.0.2 in order to be able to use later a proper version number, If
> I'd use 2 now than any other sane version later such as 1.0 will be
> lower and I'll have to use a prefix to fix that. It would be nice if you
> could just use normal version numbers from the start so the Debian
> version number will be the same as your version number.
>
>   

Well, I'd have thought that the natural numbers are a perfectly sane 
numbering scheme.  However, I'll bow to tradition and the next release 
will be 0.3.

> Some other issues I had with packaging were clean targets that are
> either missing or incomplete. You can take a look at the .diff.gz file
> that is in http://people.debian.org/~baruch/kvm/ to see all the changes
> I needed to do to the package to build it. It is rather messy right now
> but you might be able to get some things you can incorporate in order to
> make packaging easier.
>   

My current tree has fixes for most of the problems.  I'll look at the 
clean targets (why are they necessary for packaging?)


-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  parent reply	other threads:[~2006-11-15  7:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-15  7:12 Versioning of KVM Baruch Even
     [not found] ` <20061115071251.GN28027-xGn4Jn0woyz+OtfAA3OxFg@public.gmane.org>
2006-11-15  7:50   ` Avi Kivity [this message]
     [not found]     ` <455AC6D7.4060906-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-11-15  7:56       ` Baruch Even
     [not found]         ` <20061115075647.GP28027-xGn4Jn0woyz+OtfAA3OxFg@public.gmane.org>
2006-11-15  8:00           ` Avi Kivity
     [not found]             ` <455AC91D.4050704-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-11-15  8:19               ` Baruch Even

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=455AC6D7.4060906@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=baruch-6P1Dz+XQpLLYtjvyW6yDsg@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.