[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PULL 0/6] Ui 20171005 patches
From: |
Peter Maydell |
Subject: |
Re: [Qemu-devel] [PULL 0/6] Ui 20171005 patches |
Date: |
Thu, 5 Oct 2017 17:05:32 +0100 |
On 5 October 2017 at 16:55, Daniel P. Berrange <address@hidden> wrote:
> Am I right in thinking from this snippet, that you applied the patch
> series to an existing checkout with built files and then just did a
> 'make', as opposed todoing a git clean + configure + make sequence.
I did what I usually do: I did a git merge of the pull request
and applied my usual set of build tests, some of which do a 'make clean'
and some of which do incremental make (and none of which do a git
clean). This needs to work because incremental build is a very common
workflow...
thanks
-- PMM
- [Qemu-devel] [PULL 0/6] Ui 20171005 patches, Gerd Hoffmann, 2017/10/05
- [Qemu-devel] [PULL 4/6] ui: convert common input code to keycodemapdb, Gerd Hoffmann, 2017/10/05
- [Qemu-devel] [PULL 3/6] ui: add keycodemapdb repository as a GIT submodule, Gerd Hoffmann, 2017/10/05
- [Qemu-devel] [PULL 5/6] ui: convert key events to QKeyCodes immediately, Gerd Hoffmann, 2017/10/05
- [Qemu-devel] [PULL 2/6] docker: don't rely on submodules existing in the main checkout, Gerd Hoffmann, 2017/10/05
- [Qemu-devel] [PULL 6/6] ui: don't export qemu_input_event_new_key, Gerd Hoffmann, 2017/10/05
- [Qemu-devel] [PULL 1/6] build: automatically handle GIT submodule checkout for dtc, Gerd Hoffmann, 2017/10/05
- Re: [Qemu-devel] [PULL 0/6] Ui 20171005 patches, no-reply, 2017/10/05
- Re: [Qemu-devel] [PULL 0/6] Ui 20171005 patches, Peter Maydell, 2017/10/05