From: "Daniel P. Berrange" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Eric Blake" <eblake@redhat.com>,
"Lluís Vilanova" <vilanova@ac.upc.edu>,
"Gerd Hoffmann" <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 00/40] Split up the trace-events file
Date: Thu, 16 Jun 2016 14:07:59 +0100 [thread overview]
Message-ID: <20160616130759.GI11426@redhat.com> (raw)
In-Reply-To: <CAFEAcA-Uogn_D8b7Zcpp90Lx_BmqCTJQRdPdtytrrwPN=q1n_A@mail.gmail.com>
On Thu, Jun 16, 2016 at 02:00:54PM +0100, Peter Maydell wrote:
> On 16 June 2016 at 09:39, Daniel P. Berrange <berrange@redhat.com> wrote:
> > This series splits up trace-events so that there is
> > one trace-events file per sub-directory that has
> > tracing events defined. This means that the trace-events
> > files now get assoociated with the subsystem maintainers
> > if you run get_maintainer.pl on a patch. It also means
> > that responsibility for resolving conflicts is now
> > delegated to subsystem maintainers, and overall such
> > conflicts should be much rarer.
>
> Do you have a command line rune to sanity check that the
> split files have identical content to the old single file?
> That would be handy when it comes to merging this into master
> to check that any conflicts got resolved correctly.
Sure, this is what I used to check we didn't loose anything:
$ git checkout master
perl -e 'while (<>) { next if /^\s*$/; next if /^\s*#/; print }' trace-events | sort > old.txt
$ git checkout trace-events
perl -e 'while (<>) { next if /^\s*$/; next if /^\s*#/; print }' `find -name trace-events` | sort > new.txt
$ diff old.txt new.txt
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2016-06-16 13:08 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 8:39 [Qemu-devel] [PATCH v2 00/40] Split up the trace-events file Daniel P. Berrange
2016-06-16 8:39 ` [Qemu-devel] [PATCH v2 01/40] trace: add build framework for merging trace-events files Daniel P. Berrange
2016-06-16 8:39 ` [Qemu-devel] [PATCH v2 02/40] trace: split out trace events for util/ directory Daniel P. Berrange
2016-06-16 8:39 ` [Qemu-devel] [PATCH v2 03/40] trace: split out trace events for crypto/ directory Daniel P. Berrange
2016-06-16 8:39 ` [Qemu-devel] [PATCH v2 04/40] trace: split out trace events for io/ directory Daniel P. Berrange
2016-06-16 8:39 ` [Qemu-devel] [PATCH v2 05/40] trace: split out trace events for migration/ directory Daniel P. Berrange
2016-06-16 8:39 ` [Qemu-devel] [PATCH v2 06/40] trace: split out trace events for block/ directory Daniel P. Berrange
2016-06-16 8:39 ` [Qemu-devel] [PATCH v2 07/40] trace: split out trace events for hw/block/ directory Daniel P. Berrange
2016-06-16 8:39 ` [Qemu-devel] [PATCH v2 08/40] trace: split out trace events for hw/char/ directory Daniel P. Berrange
2016-06-16 8:39 ` [Qemu-devel] [PATCH v2 09/40] trace: split out trace events for hw/intc/ directory Daniel P. Berrange
2016-06-16 8:39 ` [Qemu-devel] [PATCH v2 10/40] trace: split out trace events for hw/net/ directory Daniel P. Berrange
2016-06-16 8:39 ` [Qemu-devel] [PATCH v2 11/40] trace: split out trace events for hw/virtio/ directory Daniel P. Berrange
2016-06-16 8:39 ` [Qemu-devel] [PATCH v2 12/40] trace: split out trace events for hw/audio/ directory Daniel P. Berrange
2016-06-16 8:39 ` [Qemu-devel] [PATCH v2 13/40] trace: split out trace events for hw/misc/ directory Daniel P. Berrange
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 14/40] trace: split out trace events for hw/usb/ directory Daniel P. Berrange
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 15/40] trace: split out trace events for hw/scsi/ directory Daniel P. Berrange
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 16/40] trace: split out trace events for hw/nvram/ directory Daniel P. Berrange
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 17/40] trace: split out trace events for hw/display/ directory Daniel P. Berrange
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 18/40] trace: split out trace events for hw/input/ directory Daniel P. Berrange
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 19/40] trace: split out trace events for hw/timer/ directory Daniel P. Berrange
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 20/40] trace: split out trace events for hw/dma/ directory Daniel P. Berrange
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 21/40] trace: split out trace events for hw/sparc/ directory Daniel P. Berrange
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 22/40] trace: split out trace events for hw/sd/ directory Daniel P. Berrange
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 23/40] trace: split out trace events for hw/isa/ directory Daniel P. Berrange
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 24/40] trace: split out trace events for hw/i386/ directory Daniel P. Berrange
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 25/40] trace: split out trace events for hw/9pfs/ directory Daniel P. Berrange
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 26/40] trace: split out trace events for hw/ppc/ directory Daniel P. Berrange
2016-06-16 9:49 ` Thomas Huth
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 27/40] trace: split out trace events for hw/pci/ directory Daniel P. Berrange
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 28/40] trace: split out trace events for hw/s390x/ directory Daniel P. Berrange
2016-06-16 9:57 ` Cornelia Huck
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 29/40] trace: split out trace events for hw/vfio/ directory Daniel P. Berrange
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 30/40] trace: split out trace events for hw/acpi/ directory Daniel P. Berrange
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 31/40] trace: split out trace events for hw/arm/ directory Daniel P. Berrange
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 32/40] trace: split out trace events for hw/alpha/ directory Daniel P. Berrange
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 33/40] trace: split out trace events for ui/ directory Daniel P. Berrange
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 34/40] trace: split out trace events for audio/ directory Daniel P. Berrange
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 35/40] trace: split out trace events for net/ directory Daniel P. Berrange
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 36/40] trace: split out trace events for target-sparc/ directory Daniel P. Berrange
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 37/40] trace: split out trace events for target-s390x/ directory Daniel P. Berrange
2016-06-16 9:58 ` Cornelia Huck
2016-06-17 13:29 ` Stefan Hajnoczi
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 38/40] trace: split out trace events for target-ppc/ directory Daniel P. Berrange
2016-06-16 9:51 ` Thomas Huth
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 39/40] trace: split out trace events for qom/ directory Daniel P. Berrange
2016-06-16 8:40 ` [Qemu-devel] [PATCH v2 40/40] trace: split out trace events for linux-user/ directory Daniel P. Berrange
2016-06-16 12:51 ` Laurent Vivier
2016-06-16 13:00 ` [Qemu-devel] [PATCH v2 00/40] Split up the trace-events file Peter Maydell
2016-06-16 13:07 ` Daniel P. Berrange [this message]
2016-06-17 13:30 ` Stefan Hajnoczi
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=20160616130759.GI11426@redhat.com \
--to=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vilanova@ac.upc.edu \
/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).