All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: "Daniel P. Berrange" <berrange@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>
Cc: Richard Henderson <richard.henderson@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 00/11] Disassembler patches
Date: Thu, 26 Oct 2017 10:29:59 -0300	[thread overview]
Message-ID: <8774f2a0-274f-b358-c316-d3484f15b2cb@amsat.org> (raw)
In-Reply-To: <20171026100645.GA24581@redhat.com>

On 10/26/2017 07:06 AM, Daniel P. Berrange wrote:
> Do we really expect make/configure todo the right thing when going
> backwards in time ?

"Yes"? Ideally at least :)

> I've always assumed that if you go back in time
> when you need to do a 'git clean -f -x d' and re-run configure from> scratch.
I certainly don't do that and would rather not have to think about it.

I also don't think about calling it when bisecting, however looking at
the man page, this is somehow suggested in the example:

·   Automatically bisect with temporary modifications (hot-fix):
[...]
        # undo the tweak to allow clean flipping to the next commit
        git reset --hard

This could be a warning displayed via a post-checkout hook, for this
particular merge hash, or if you go way too back in time...

> Certainly in the past various makefile changes in QEMU would> break, or silently not correctly recompile stuff when going backwards
> in time.

Travis is already taking too long, but we could add a such test
(merge/build/checkout backward/configure/quick build), not sure if we
gain much.

  reply	other threads:[~2017-10-26 13:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-25 12:30 [Qemu-devel] [PULL 00/11] Disassembler patches Richard Henderson
2017-10-25 12:30 ` [Qemu-devel] [PULL 01/11] target/i386: Convert to disas_set_info hook Richard Henderson
2017-10-25 12:30 ` [Qemu-devel] [PULL 02/11] target/ppc: " Richard Henderson
2017-10-25 12:30 ` [Qemu-devel] [PULL 03/11] target/arm: Move BE32 disassembler fixup Richard Henderson
2017-10-25 12:30 ` [Qemu-devel] [PULL 04/11] target/arm: Don't set INSN_ARM_BE32 for CONFIG_USER_ONLY Richard Henderson
2017-10-25 12:30 ` [Qemu-devel] [PULL 05/11] disas: Remove unused flags arguments Richard Henderson
2017-10-25 12:30 ` [Qemu-devel] [PULL 06/11] disas: Support the Capstone disassembler library Richard Henderson
2017-10-25 12:30 ` [Qemu-devel] [PULL 07/11] i386: Support Capstone in disas_set_info Richard Henderson
2017-10-25 12:30 ` [Qemu-devel] [PULL 08/11] arm: " Richard Henderson
2017-10-25 12:30 ` [Qemu-devel] [PULL 09/11] ppc: " Richard Henderson
2017-10-25 12:30 ` [Qemu-devel] [PULL 10/11] disas: Remove monitor_disas_is_physical Richard Henderson
2017-10-25 12:30 ` [Qemu-devel] [PULL 11/11] disas: Add capstone as submodule Richard Henderson
2017-10-25 12:43 ` [Qemu-devel] [PULL 00/11] Disassembler patches no-reply
2017-10-26  6:07 ` Peter Maydell
2017-10-26  6:16   ` Peter Maydell
2017-10-26  7:06     ` Daniel P. Berrange
2017-10-26  7:21       ` Peter Maydell
2017-10-26 10:04         ` Richard Henderson
2017-10-26 10:06         ` Daniel P. Berrange
2017-10-26 13:29           ` Philippe Mathieu-Daudé [this message]
2017-10-26 13:50             ` Daniel P. Berrange
2017-10-26 14:25           ` Peter Maydell
2017-10-26  7:10   ` Richard Henderson
2017-10-27 15:07 ` Eric Blake

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=8774f2a0-274f-b358-c316-d3484f15b2cb@amsat.org \
    --to=f4bug@amsat.org \
    --cc=berrange@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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.