All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: (V2) tools/python: Clean python correctly
Date: Tue, 14 Aug 2012 18:41:43 +0100	[thread overview]
Message-ID: <502A8DD7.3080504@citrix.com> (raw)
In-Reply-To: <20522.35865.492083.486374@mariner.uk.xensource.com>

On 14/08/12 18:34, Ian Jackson wrote:
> Andrew Cooper writes ("Re: [Xen-devel] (V2) tools/python: Clean python correctly"):
>> Attached version 2, because it seems that despite my testing, "python
>> setup.py clean" still doesn't actually clean enough.
>>
>> On 14/08/12 15:10, Andrew Cooper wrote:
>>> I discovered this with repeated calls to "make clean; make dist-tools"
>>>
>>> An alternative, if you wish to remove the use of $(PYTHON) from the
>>> clean path is to just `rm -rf build`, but using setup.py seems neater.
> Perhaps removing the build directory would be better and faster and
> more reliable ?
>
> Ian.

That would put the code in line with tools/pygrub.  Sec while I make a
v3 patch

-- 
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com

  reply	other threads:[~2012-08-14 17:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-14 14:10 tools/python: Clean python correctly Andrew Cooper
2012-08-14 16:54 ` (V2) " Andrew Cooper
2012-08-14 17:34   ` Ian Jackson
2012-08-14 17:41     ` Andrew Cooper [this message]
2012-08-14 17:45       ` (V3) " Andrew Cooper
2012-08-17 13:48         ` Ian Campbell

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=502A8DD7.3080504@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.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.