From: Ian Campbell <ian.campbell@citrix.com>
To: Doug Goldstein <cardoe@cardoe.com>, xen-devel@lists.xen.org
Subject: Re: [PATCH for 4.6] build: fix tarball stubdom build
Date: Fri, 4 Sep 2015 14:54:45 +0100 [thread overview]
Message-ID: <1441374885.26292.511.camel@citrix.com> (raw)
In-Reply-To: <55E9A121.3060901@cardoe.com>
On Fri, 2015-09-04 at 08:48 -0500, Doug Goldstein wrote:
> On 8/27/15 12:58 PM, Ian Jackson wrote:
> > Wei Liu writes ("[PATCH for 4.6] build: fix tarball stubdom build"):
> > > When we create a source code tarball, mini-os is extracted to
> > > extras/mini-os directory. When building a source code tarball, we
> > > shouldn't clone mini-os again.
> > >
> > > Only clone mini-os when that directory doesn't exist. This fixes
> > > tarball
> > > build and doesn't affect non-tarball build.
> >
> > Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
> >
> > I am about to commit this.
> >
> > Thanks,
> > Ian.
>
> Ping. Do we want this to land for 4.6?
It is:
commit 0cc73e9870a96e18fc076618c0b419919794ae06
Author: Wei Liu <wei.liu2@citrix.com>
Date: Thu Aug 27 16:54:01 2015 +0100
build: fix tarball stubdom build
> Since all its doing is
> documenting the Makefile targets in the actual 4.6 Makefile I would
> think its safe.
But that makes me think you hit rpely on the wrong email.
If you meant "build: update top-level make help" then that is mentioned in
http://lists.xen.org/archives/html/xen-devel/2015-09/msg00533.html (and
I've not read Wei's reply yet)
Ian.
prev parent reply other threads:[~2015-09-04 13:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 15:54 [PATCH for 4.6] build: fix tarball stubdom build Wei Liu
2015-08-27 16:05 ` Jan Beulich
2015-08-27 16:24 ` Wei Liu
2015-08-28 6:41 ` Jan Beulich
2015-08-28 8:47 ` Wei Liu
2015-08-28 9:49 ` Jan Beulich
2015-08-28 9:55 ` Wei Liu
2015-08-27 17:58 ` Ian Jackson
2015-09-04 13:48 ` Doug Goldstein
2015-09-04 13:54 ` Ian Campbell [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=1441374885.26292.511.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=cardoe@cardoe.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).