All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Gerd Hoffmann <kraxel@redhat.com>,
	Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] build: add make dist target (v2)
Date: Wed, 18 Jul 2012 08:55:32 -0500	[thread overview]
Message-ID: <87d33t897v.fsf@codemonkey.ws> (raw)
In-Reply-To: <5006BCB4.1010502@redhat.com>

Gerd Hoffmann <kraxel@redhat.com> writes:

> On 07/17/12 21:12, Michael Roth wrote:
>> On Tue, Jul 17, 2012 at 01:33:32PM -0500, Anthony Liguori wrote:
>>> Let's stop screwing up releases by having a script do the work that Anthony's
>>> fat fingers can't seem to get right.
>>>
>>> Cc: Michael Roth <mdroth@linux.vnet.ibm.com>
>>> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
>> 
>> Breaks if there's no tag corresponding with the contents of VERSION,
>> but that might be considered a feature (an alternative might be to
>> assume it's a development release, use current HEAD for master, and append the
>> short git hash to the version). Works well as far as I can tell though,
>> and I made a special point to confirm it did indeed output a bz2 :)
>
> Or just use 'git describe --long' to figure what the version is.  This
> way you can easily build a tarball for any git commit, and a release
> tarball is just 'git checkout v$version; make dist'.

As long as it doesn't break release tarballs, I'm very open to patches
to make this more generally useful.

Regards,

Anthony Liguori

>
> cheers,
>   Gerd

  reply	other threads:[~2012-07-18 13:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17 18:33 [Qemu-devel] [PATCH] build: add make dist target (v2) Anthony Liguori
2012-07-17 18:50 ` Eric Blake
2012-07-17 19:12 ` Michael Roth
2012-07-18 13:40   ` Gerd Hoffmann
2012-07-18 13:55     ` Anthony Liguori [this message]
2012-07-18 14:07 ` Daniel P. Berrange

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=87d33t897v.fsf@codemonkey.ws \
    --to=aliguori@us.ibm.com \
    --cc=kraxel@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --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.