From: Avi Kivity <avi@qumranet.com>
To: Ryota OZAKI <ozaki.ryota@gmail.com>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: [PATCH] 'make clean' is eager to delete config.mak files
Date: Sun, 23 Mar 2008 11:03:05 +0200 [thread overview]
Message-ID: <47E61CC9.2080000@qumranet.com> (raw)
In-Reply-To: <5e93dcec0803220916s50d363dbwb5c25bf844d41f44@mail.gmail.com>
Ryota OZAKI wrote:
> Hi all,
>
> Current 'make clean' deletes config.mak files so
> that we have to ./configure again after doing that.
> This behavior is different from that of standard
> 'make clean'.
>
> This patch introduces 'make distclean' to delete
> config.mak files instead of 'make clean', following
> a standard manner of Makefile.
>
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
prev parent reply other threads:[~2008-03-23 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-22 16:16 [PATCH] 'make clean' is eager to delete config.mak files Ryota OZAKI
2008-03-23 9:03 ` Avi Kivity [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=47E61CC9.2080000@qumranet.com \
--to=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=ozaki.ryota@gmail.com \
/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