From: George Dunlap <george.dunlap@eu.citrix.com>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: Ian Jackson <ian.jackson@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Jan Beulich <jbeulich@suse.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH 2/2] make: Make "src-tarball" target actually make a source tarball
Date: Thu, 3 Jul 2014 12:25:25 +0100 [thread overview]
Message-ID: <53B53DA5.8030401@eu.citrix.com> (raw)
In-Reply-To: <20140703112233.GC1635@perard.uk.xensource.com>
On 07/03/2014 12:22 PM, Anthony PERARD wrote:
> On Wed, Jul 02, 2014 at 05:15:12PM +0100, George Dunlap wrote:
>> At the moment, making a release tarball is an annoyingly manual
>> process that involves running "git archive" into a temporary directory.
> Does the source tarball would need to includes tarball of ipxe and the
> different stuff to build a stubdom ?
At the moment, AFAIK, the normal xen release tarballs do not.
We could call this target "release-tarball" instead.
>
>> +xen_root=$1
>> +desc=$2
>> +
>> +tdir=$(mktemp -d $xen_root/dist/xen.XXXXXXXX) || exit 1
> Many missing " around variables, better safe than sorry :).
Ack.
-George
next prev parent reply other threads:[~2014-07-03 11:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 16:15 [PATCH 1/2] make: Check tools/qemu-xen[-traditional] for qemu before downloading George Dunlap
2014-07-02 16:15 ` [PATCH 2/2] make: Make "src-tarball" target actually make a source tarball George Dunlap
2014-07-03 8:29 ` Ian Campbell
2014-07-03 12:48 ` George Dunlap
2014-07-03 13:46 ` Ian Campbell
2014-07-08 9:50 ` Ian Jackson
2014-07-08 11:00 ` George Dunlap
2014-07-03 11:22 ` Anthony PERARD
2014-07-03 11:25 ` George Dunlap [this message]
2014-07-03 8:25 ` [PATCH 1/2] make: Check tools/qemu-xen[-traditional] for qemu before downloading Ian Campbell
2014-07-03 9:04 ` George Dunlap
2014-07-03 9:10 ` Ian Campbell
2014-07-08 9:57 ` Ian Jackson
2014-07-08 10:57 ` George Dunlap
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=53B53DA5.8030401@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=anthony.perard@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=jbeulich@suse.com \
--cc=xen-devel@lists.xen.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.