From: George Dunlap <george.dunlap@eu.citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [xen-4.3-testing bisection] complete build-i386
Date: Thu, 11 Jul 2013 16:13:19 +0100 [thread overview]
Message-ID: <51DECB8F.30401@eu.citrix.com> (raw)
In-Reply-To: <20958.51758.203720.25162@mariner.uk.xensource.com>
On 11/07/13 16:07, Ian Jackson wrote:
> If someone did an ad-hoc test build of changing Config.mk, it is
> possible that this is because one of
>
> (a) They didn't clean their tree _entirely thoroughly_.
> "make clean" is not sufficient because it doesn't remove cloned
> subdirectories. "git-clean -x -d -f" is not sufficient because
> it recurses into the cloned subdirectories, discovers that these
> are separate git repositories, and stops.
If you specify -f twice it will override this behavior and delete cloned
subdirectories. So "git clean -ffdx" should really really really clean it.
-George
next prev parent reply other threads:[~2013-07-11 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 11:44 [xen-4.3-testing bisection] complete build-i386 xen.org
2013-07-11 15:07 ` Ian Jackson
2013-07-11 15:13 ` George Dunlap [this message]
2013-07-11 16:10 ` George Dunlap
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=51DECB8F.30401@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).