From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Programmingkid <programmingkidx@gmail.com>,
Thomas Huth <thuth@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] configure: Change capstone's default state to disabled
Date: Mon, 13 May 2019 10:50:21 +0100 [thread overview]
Message-ID: <20190513095021.GC15029@redhat.com> (raw)
In-Reply-To: <CAFEAcA9GamvcCmbxgcLNoSxKiJnMk-7p__13ct8GOuVQUM6KXQ@mail.gmail.com>
On Mon, May 13, 2019 at 10:48:58AM +0100, Peter Maydell wrote:
> On Mon, 13 May 2019 at 10:08, Daniel P. Berrangé <berrange@redhat.com> wrote:
> >
> > On Sun, May 12, 2019 at 03:47:49PM +0200, Thomas Huth wrote:
> > > Maybe try to clean the folder first:
> > >
> > > rm -r capstone
> > > mkdir capstone
> > > make git-submodule-update
> > >
> > > If that does not help, maybe try a completely fresh git checkout?
> >
> > Rather than deleting stuff like that, it is best to use git to put your
> > dir back to a clean state.
> >
> > git submodule deinit --all --force
> > git clean -f -x -d
>
> That git clean line will blow away any untracked files in
> your entire tree, won't it? If so, better move anything
> you cared about somewhere else first...
Yes, git clean blows away everything that isn't tracked.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2019-05-13 9:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 22:47 [Qemu-devel] [PATCH] configure: Change capstone's default state to disabled John Arbuckle
2019-04-18 22:47 ` John Arbuckle
2019-04-19 7:10 ` Thomas Huth
2019-04-19 7:10 ` Thomas Huth
2019-04-19 13:44 ` G 3
2019-04-19 13:44 ` G 3
2019-04-19 18:22 ` Richard Henderson
2019-04-19 18:22 ` Richard Henderson
2019-04-19 23:48 ` Programmingkid
2019-04-19 23:48 ` Programmingkid
2019-04-20 10:40 ` Thomas Huth
2019-04-20 10:40 ` Thomas Huth
2019-05-11 17:21 ` Programmingkid
2019-05-11 18:05 ` Thomas Huth
2019-05-11 18:28 ` Programmingkid
2019-05-12 13:47 ` Thomas Huth
2019-05-13 9:08 ` Daniel P. Berrangé
2019-05-13 9:48 ` Peter Maydell
2019-05-13 9:50 ` Daniel P. Berrangé [this message]
2019-05-15 3:30 ` Programmingkid
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=20190513095021.GC15029@redhat.com \
--to=berrange@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=programmingkidx@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.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).