From: Doug Goldstein <cardoe@cardoe.com>
To: Jan Beulich <JBeulich@suse.com>, Ian Campbell <ian.campbell@citrix.com>
Cc: Keir Fraser <keir@xen.org>, Tim Deegan <tim@xen.org>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH] build: update top-level make help
Date: Wed, 2 Sep 2015 09:22:19 -0500 [thread overview]
Message-ID: <55E7061B.7060208@cardoe.com> (raw)
In-Reply-To: <55E7207C020000780009F0E4@prv-mh.provo.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 2129 bytes --]
On 9/2/15 9:14 AM, Jan Beulich wrote:
>>>> On 02.09.15 at 15:34, <ian.campbell@citrix.com> wrote:
>> On Wed, 2015-09-02 at 07:14 -0600, Jan Beulich wrote:
>>>>>> On 02.09.15 at 15:09, <cardoe@cardoe.com> wrote:
>>>> On Wed, Sep 2, 2015 at 3:28 AM, Jan Beulich <jbeulich@suse.com> wrote:
>>>>>>>> Doug Goldstein <cardoe@cardoe.com> 09/01/15 10:10 PM >>>
>>>>>> --- a/Makefile
>>>>>> +++ b/Makefile
>>>>>> @@ -228,16 +228,23 @@ help:
>>>>>> @echo ' install-stubdom - build and install the stubdomain
>>>>>> images'
>>>>>> @echo ' install-docs - build and install user
>>>>>> documentation'
>>>>>> @echo ''
>>>>>> - @echo 'Building targets:'
>>>>>> + @echo 'Local dist targets:'
>>>>>> @echo ' dist - build and install everything into
>>>>>> local dist directory'
>>>>>> @echo ' world - clean everything then make dist'
>>>>>> - @echo ' xen - build and install Xen
>>>>>> hypervisor'
>>>>>> - @echo ' tools - build and install tools'
>>>>>> - @echo ' stubdom - build and install the
>>>>>> stubdomain images'
>>>>>> - @echo ' docs - build and install user
>>>>>> documentation'
>>>>>
>>>>> Why are these being removed? At least the xen and tools ones work
>>>>> fine for me.
>>>>
>>>> In the makefile they're marked as "legacy" and they are wired straight
>>>> to their "dist-" equivalents.
>>>
>>> But still they're there and they work (and they're faster to type than
>>> their "dist-" equivalents).
>>
>> If they are legacy then it is correct to not list them here.
>
> Hmm - why does "legacy" imply "not documented here"?
>
> But anyway - I don't mean to stand in the way of you committing the
> patch as is, as long as those (legacy) build targets don't go away.
>
> Jan
>
I definitely had no intention of removing them. I was merely trying to
update the help output to match what I saw when reading the contents of
the Makefile.
Do I still need to resubmit or is my S-o-b on the ML ok?
--
Doug Goldstein
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 959 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-09-02 14:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 20:10 [PATCH] build: update top-level make help Doug Goldstein
2015-09-02 8:28 ` Jan Beulich
2015-09-02 13:09 ` Doug Goldstein
2015-09-02 13:14 ` Jan Beulich
2015-09-02 13:34 ` Ian Campbell
2015-09-02 14:14 ` Jan Beulich
2015-09-02 14:22 ` Doug Goldstein [this message]
2015-09-02 14:31 ` Ian Campbell
2015-09-04 14:41 ` Ian Campbell
2015-09-02 14:26 ` Ian Campbell
2015-09-02 14:55 ` 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=55E7061B.7060208@cardoe.com \
--to=cardoe@cardoe.com \
--cc=JBeulich@suse.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--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.