From: George Dunlap <george.dunlap@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
Jan Beulich <jbeulich@suse.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH 5/5] make: Make "src-tarball" target actually make a source tarball
Date: Wed, 16 Jul 2014 18:45:33 +0100 [thread overview]
Message-ID: <53C6BA3D.5060403@eu.citrix.com> (raw)
In-Reply-To: <1405529773.1087.88.camel@kazak.uk.xensource.com>
On 07/16/2014 05:56 PM, Ian Campbell wrote:
> On Wed, 2014-07-16 at 16:06 +0100, Ian Jackson wrote:
>> George Dunlap writes ("[PATCH 5/5] make: Make "src-tarball" target actually make a source tarball"):
>>> At the moment, making a release tarball is an annoyingly manual
>>> process that involves running "git archive" into a temporary directory.
>> ...
>>> +src-tarball: subtree-update
>>> + bash ./tools/misc/mktarball $(XEN_ROOT) $$(git describe)
>>
>> Does this absolutely have to depend on subtree-update ? Perhaps we
>> need a new "make the subtrees exist" target ?
>
> Given that he makes the force targets depend on the dir targets in one
> of the earlier patches I think subtree-update might already be that
> target...
I think he might have been thinking that it would be nice to be able to
make a tarball without doing the force update -- i.e., if you had
checked out a particular version of one of the trees, just use that; but
if you hadn't checked anything out, go fetch the tree.
I could do that. :-) It means SOP would have to be two steps "make
subdir-update ; make src-tarball-release". Personally I think it's a
bit of a trap waiting to happen, but I can see the logic behind it.
-George
next prev parent reply other threads:[~2014-07-16 17:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 16:15 [PATCH 1/5] make: Check tools/qemu-xen[-traditional] for qemu before downloading George Dunlap
2014-07-14 16:15 ` [PATCH 2/5] make: Normalize config options for external trees George Dunlap
2014-07-16 8:58 ` Ian Campbell
2014-07-16 14:53 ` Ian Jackson
2014-07-21 10:22 ` Olaf Hering
2014-07-21 10:28 ` George Dunlap
2014-07-21 10:44 ` Olaf Hering
2014-07-21 10:46 ` George Dunlap
2014-07-21 10:49 ` Olaf Hering
2014-07-14 16:15 ` [PATCH 3/5] make: Make *-dir-force-update depend on *-dir-find George Dunlap
2014-07-16 14:53 ` Ian Jackson
2014-07-14 16:15 ` [PATCH 4/5] make: Add subtree-update target George Dunlap
2014-07-16 9:00 ` Ian Campbell
2014-07-16 14:54 ` Ian Jackson
2014-07-14 16:15 ` [PATCH 5/5] make: Make "src-tarball" target actually make a source tarball George Dunlap
2014-07-16 15:06 ` Ian Jackson
2014-07-16 16:56 ` Ian Campbell
2014-07-16 17:45 ` George Dunlap [this message]
2014-07-17 9:21 ` Ian Campbell
2014-07-17 16:46 ` George Dunlap
2014-07-18 10:45 ` Ian Jackson
2014-09-15 15:42 ` George Dunlap
2014-09-15 15:46 ` Ian Jackson
2014-07-16 9:02 ` [PATCH 1/5] make: Check tools/qemu-xen[-traditional] for qemu before downloading Ian Campbell
2014-07-16 14:50 ` Ian Jackson
2014-07-18 12:39 ` Ian Campbell
2014-07-23 10:52 ` Jan Beulich
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=53C6BA3D.5060403@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=anthony.perard@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).