gitignore: anchor all ignored names
by default, patterns/names in .gitignore are applied
recursively to all subdirectories. So any name mentioned
in .gitignore is ignored in all subdirectores. This is good
for, say. object files (*.o), but not good for particular
names which should be ignored only in one directory. For
example, qemu-img.1 file is generated in the top directory,
and it should be ignored only there, not in some subdir.
At first, this might not matter much, but we have lots of
examples already where it actually does not help at all.
For example, top-level .gitignore ignores a file/dir named
"patches" (which is very questionable by itself), but it
is applied recursively, so git also ignores, for example,
debian/patches/ which should not be ignored.
So anchor all the names where appropriate. .gitignore
should be cleaned up further, which will be addressed in
a subsequent patch.
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
2014-02-11 14:22:32 +04:00
|
|
|
/config-devices.*
|
|
|
|
|
/config-all-devices.*
|
|
|
|
|
/config-all-disas.*
|
|
|
|
|
/config-host.*
|
|
|
|
|
/config-target.*
|
|
|
|
|
/config.status
|
2014-05-23 20:07:24 +04:00
|
|
|
/config-temp
|
2016-06-16 11:39:47 +03:00
|
|
|
/trace-events-all
|
gitignore: anchor all ignored names
by default, patterns/names in .gitignore are applied
recursively to all subdirectories. So any name mentioned
in .gitignore is ignored in all subdirectores. This is good
for, say. object files (*.o), but not good for particular
names which should be ignored only in one directory. For
example, qemu-img.1 file is generated in the top directory,
and it should be ignored only there, not in some subdir.
At first, this might not matter much, but we have lots of
examples already where it actually does not help at all.
For example, top-level .gitignore ignores a file/dir named
"patches" (which is very questionable by itself), but it
is applied recursively, so git also ignores, for example,
debian/patches/ which should not be ignored.
So anchor all the names where appropriate. .gitignore
should be cleaned up further, which will be addressed in
a subsequent patch.
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
2014-02-11 14:22:32 +04:00
|
|
|
/trace/generated-events.h
|
|
|
|
|
/trace/generated-events.c
|
2014-05-30 16:12:01 +04:00
|
|
|
/trace/generated-helpers-wrappers.h
|
2014-05-30 16:11:50 +04:00
|
|
|
/trace/generated-helpers.h
|
2014-05-30 16:11:56 +04:00
|
|
|
/trace/generated-helpers.c
|
2014-05-30 16:12:13 +04:00
|
|
|
/trace/generated-tcg-tracers.h
|
2015-06-23 15:30:20 +03:00
|
|
|
/ui/shader/texture-blit-frag.h
|
|
|
|
|
/ui/shader/texture-blit-vert.h
|
2017-10-20 10:09:14 +03:00
|
|
|
/ui/shader/texture-blit-flip-vert.h
|
2017-09-29 13:11:58 +03:00
|
|
|
/ui/input-keymap-*.c
|
2010-10-07 15:07:15 +04:00
|
|
|
*-timestamp
|
gitignore: anchor all ignored names
by default, patterns/names in .gitignore are applied
recursively to all subdirectories. So any name mentioned
in .gitignore is ignored in all subdirectores. This is good
for, say. object files (*.o), but not good for particular
names which should be ignored only in one directory. For
example, qemu-img.1 file is generated in the top directory,
and it should be ignored only there, not in some subdir.
At first, this might not matter much, but we have lots of
examples already where it actually does not help at all.
For example, top-level .gitignore ignores a file/dir named
"patches" (which is very questionable by itself), but it
is applied recursively, so git also ignores, for example,
debian/patches/ which should not be ignored.
So anchor all the names where appropriate. .gitignore
should be cleaned up further, which will be addressed in
a subsequent patch.
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
2014-02-11 14:22:32 +04:00
|
|
|
/*-softmmu
|
|
|
|
|
/*-darwin-user
|
|
|
|
|
/*-linux-user
|
|
|
|
|
/*-bsd-user
|
2015-10-26 23:27:31 +03:00
|
|
|
/ivshmem-client
|
|
|
|
|
/ivshmem-server
|
2014-04-27 15:02:26 +04:00
|
|
|
/libdis*
|
|
|
|
|
/libuser
|
gitignore: anchor all ignored names
by default, patterns/names in .gitignore are applied
recursively to all subdirectories. So any name mentioned
in .gitignore is ignored in all subdirectores. This is good
for, say. object files (*.o), but not good for particular
names which should be ignored only in one directory. For
example, qemu-img.1 file is generated in the top directory,
and it should be ignored only there, not in some subdir.
At first, this might not matter much, but we have lots of
examples already where it actually does not help at all.
For example, top-level .gitignore ignores a file/dir named
"patches" (which is very questionable by itself), but it
is applied recursively, so git also ignores, for example,
debian/patches/ which should not be ignored.
So anchor all the names where appropriate. .gitignore
should be cleaned up further, which will be addressed in
a subsequent patch.
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
2014-02-11 14:22:32 +04:00
|
|
|
/linux-headers/asm
|
2014-03-10 22:08:59 +04:00
|
|
|
/qga/qapi-generated
|
2018-02-26 22:48:58 +03:00
|
|
|
/qapi-gen-timestamp
|
2018-02-11 12:36:05 +03:00
|
|
|
/qapi/qapi-builtin-types.[ch]
|
|
|
|
|
/qapi/qapi-builtin-visit.[ch]
|
qapi: Generate separate .h, .c for each module
Our qapi-schema.json is composed of modules connected by include
directives, but the generated code is monolithic all the same: one
qapi-types.h with all the types, one qapi-visit.h with all the
visitors, and so forth. These monolithic headers get included all
over the place. In my "build everything" tree, adding a QAPI type
recompiles about 4800 out of 5100 objects.
We wouldn't write such monolithic headers by hand. It stands to
reason that we shouldn't generate them, either.
Split up generated qapi-types.h to mirror the schema's modular
structure: one header per module. Name the main module's header
qapi-types.h, and sub-module D/B.json's header D/qapi-types-B.h.
Mirror the schema's includes in the headers, so that qapi-types.h gets
you everything exactly as before. If you need less, you can include
one or more of the sub-module headers. To be exploited shortly.
Split up qapi-types.c, qapi-visit.h, qapi-visit.c, qmp-commands.h,
qmp-commands.c, qapi-event.h, qapi-event.c the same way.
qmp-introspect.h, qmp-introspect.c and qapi.texi remain monolithic.
The split of qmp-commands.c duplicates static helper function
qmp_marshal_output_str() in qapi-commands-char.c and
qapi-commands-misc.c. This happens when commands returning the same
type occur in multiple modules. Not worth avoiding.
Since I'm going to rename qapi-event.[ch] to qapi-events.[ch], and
qmp-commands.[ch] to qapi-commands.[ch], name the shards that way
already, to reduce churn. This requires temporary hacks in
commands.py and events.py. Similarly, c_name() must temporarily
be taught to munge '/' in common.py. They'll go away with the rename.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20180211093607.27351-23-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
[eblake: declare a dummy variable in each .c file, to shut up OSX
toolchain warnings about empty .o files, including hacking c_name()]
Signed-off-by: Eric Blake <eblake@redhat.com>
2018-02-11 12:36:00 +03:00
|
|
|
/qapi/qapi-commands-block-core.[ch]
|
|
|
|
|
/qapi/qapi-commands-block.[ch]
|
|
|
|
|
/qapi/qapi-commands-char.[ch]
|
|
|
|
|
/qapi/qapi-commands-common.[ch]
|
|
|
|
|
/qapi/qapi-commands-crypto.[ch]
|
|
|
|
|
/qapi/qapi-commands-introspect.[ch]
|
|
|
|
|
/qapi/qapi-commands-migration.[ch]
|
2018-02-27 02:13:27 +03:00
|
|
|
/qapi/qapi-commands-misc.[ch]
|
qapi: Generate separate .h, .c for each module
Our qapi-schema.json is composed of modules connected by include
directives, but the generated code is monolithic all the same: one
qapi-types.h with all the types, one qapi-visit.h with all the
visitors, and so forth. These monolithic headers get included all
over the place. In my "build everything" tree, adding a QAPI type
recompiles about 4800 out of 5100 objects.
We wouldn't write such monolithic headers by hand. It stands to
reason that we shouldn't generate them, either.
Split up generated qapi-types.h to mirror the schema's modular
structure: one header per module. Name the main module's header
qapi-types.h, and sub-module D/B.json's header D/qapi-types-B.h.
Mirror the schema's includes in the headers, so that qapi-types.h gets
you everything exactly as before. If you need less, you can include
one or more of the sub-module headers. To be exploited shortly.
Split up qapi-types.c, qapi-visit.h, qapi-visit.c, qmp-commands.h,
qmp-commands.c, qapi-event.h, qapi-event.c the same way.
qmp-introspect.h, qmp-introspect.c and qapi.texi remain monolithic.
The split of qmp-commands.c duplicates static helper function
qmp_marshal_output_str() in qapi-commands-char.c and
qapi-commands-misc.c. This happens when commands returning the same
type occur in multiple modules. Not worth avoiding.
Since I'm going to rename qapi-event.[ch] to qapi-events.[ch], and
qmp-commands.[ch] to qapi-commands.[ch], name the shards that way
already, to reduce churn. This requires temporary hacks in
commands.py and events.py. Similarly, c_name() must temporarily
be taught to munge '/' in common.py. They'll go away with the rename.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20180211093607.27351-23-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
[eblake: declare a dummy variable in each .c file, to shut up OSX
toolchain warnings about empty .o files, including hacking c_name()]
Signed-off-by: Eric Blake <eblake@redhat.com>
2018-02-11 12:36:00 +03:00
|
|
|
/qapi/qapi-commands-net.[ch]
|
|
|
|
|
/qapi/qapi-commands-rocker.[ch]
|
|
|
|
|
/qapi/qapi-commands-run-state.[ch]
|
|
|
|
|
/qapi/qapi-commands-sockets.[ch]
|
|
|
|
|
/qapi/qapi-commands-tpm.[ch]
|
|
|
|
|
/qapi/qapi-commands-trace.[ch]
|
|
|
|
|
/qapi/qapi-commands-transaction.[ch]
|
|
|
|
|
/qapi/qapi-commands-ui.[ch]
|
2018-02-11 12:36:05 +03:00
|
|
|
/qapi/qapi-commands.[ch]
|
qapi: Generate separate .h, .c for each module
Our qapi-schema.json is composed of modules connected by include
directives, but the generated code is monolithic all the same: one
qapi-types.h with all the types, one qapi-visit.h with all the
visitors, and so forth. These monolithic headers get included all
over the place. In my "build everything" tree, adding a QAPI type
recompiles about 4800 out of 5100 objects.
We wouldn't write such monolithic headers by hand. It stands to
reason that we shouldn't generate them, either.
Split up generated qapi-types.h to mirror the schema's modular
structure: one header per module. Name the main module's header
qapi-types.h, and sub-module D/B.json's header D/qapi-types-B.h.
Mirror the schema's includes in the headers, so that qapi-types.h gets
you everything exactly as before. If you need less, you can include
one or more of the sub-module headers. To be exploited shortly.
Split up qapi-types.c, qapi-visit.h, qapi-visit.c, qmp-commands.h,
qmp-commands.c, qapi-event.h, qapi-event.c the same way.
qmp-introspect.h, qmp-introspect.c and qapi.texi remain monolithic.
The split of qmp-commands.c duplicates static helper function
qmp_marshal_output_str() in qapi-commands-char.c and
qapi-commands-misc.c. This happens when commands returning the same
type occur in multiple modules. Not worth avoiding.
Since I'm going to rename qapi-event.[ch] to qapi-events.[ch], and
qmp-commands.[ch] to qapi-commands.[ch], name the shards that way
already, to reduce churn. This requires temporary hacks in
commands.py and events.py. Similarly, c_name() must temporarily
be taught to munge '/' in common.py. They'll go away with the rename.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20180211093607.27351-23-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
[eblake: declare a dummy variable in each .c file, to shut up OSX
toolchain warnings about empty .o files, including hacking c_name()]
Signed-off-by: Eric Blake <eblake@redhat.com>
2018-02-11 12:36:00 +03:00
|
|
|
/qapi/qapi-events-block-core.[ch]
|
|
|
|
|
/qapi/qapi-events-block.[ch]
|
|
|
|
|
/qapi/qapi-events-char.[ch]
|
|
|
|
|
/qapi/qapi-events-common.[ch]
|
|
|
|
|
/qapi/qapi-events-crypto.[ch]
|
|
|
|
|
/qapi/qapi-events-introspect.[ch]
|
|
|
|
|
/qapi/qapi-events-migration.[ch]
|
2018-02-27 02:13:27 +03:00
|
|
|
/qapi/qapi-events-misc.[ch]
|
qapi: Generate separate .h, .c for each module
Our qapi-schema.json is composed of modules connected by include
directives, but the generated code is monolithic all the same: one
qapi-types.h with all the types, one qapi-visit.h with all the
visitors, and so forth. These monolithic headers get included all
over the place. In my "build everything" tree, adding a QAPI type
recompiles about 4800 out of 5100 objects.
We wouldn't write such monolithic headers by hand. It stands to
reason that we shouldn't generate them, either.
Split up generated qapi-types.h to mirror the schema's modular
structure: one header per module. Name the main module's header
qapi-types.h, and sub-module D/B.json's header D/qapi-types-B.h.
Mirror the schema's includes in the headers, so that qapi-types.h gets
you everything exactly as before. If you need less, you can include
one or more of the sub-module headers. To be exploited shortly.
Split up qapi-types.c, qapi-visit.h, qapi-visit.c, qmp-commands.h,
qmp-commands.c, qapi-event.h, qapi-event.c the same way.
qmp-introspect.h, qmp-introspect.c and qapi.texi remain monolithic.
The split of qmp-commands.c duplicates static helper function
qmp_marshal_output_str() in qapi-commands-char.c and
qapi-commands-misc.c. This happens when commands returning the same
type occur in multiple modules. Not worth avoiding.
Since I'm going to rename qapi-event.[ch] to qapi-events.[ch], and
qmp-commands.[ch] to qapi-commands.[ch], name the shards that way
already, to reduce churn. This requires temporary hacks in
commands.py and events.py. Similarly, c_name() must temporarily
be taught to munge '/' in common.py. They'll go away with the rename.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20180211093607.27351-23-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
[eblake: declare a dummy variable in each .c file, to shut up OSX
toolchain warnings about empty .o files, including hacking c_name()]
Signed-off-by: Eric Blake <eblake@redhat.com>
2018-02-11 12:36:00 +03:00
|
|
|
/qapi/qapi-events-net.[ch]
|
|
|
|
|
/qapi/qapi-events-rocker.[ch]
|
|
|
|
|
/qapi/qapi-events-run-state.[ch]
|
|
|
|
|
/qapi/qapi-events-sockets.[ch]
|
|
|
|
|
/qapi/qapi-events-tpm.[ch]
|
|
|
|
|
/qapi/qapi-events-trace.[ch]
|
|
|
|
|
/qapi/qapi-events-transaction.[ch]
|
|
|
|
|
/qapi/qapi-events-ui.[ch]
|
2018-02-11 12:36:05 +03:00
|
|
|
/qapi/qapi-events.[ch]
|
|
|
|
|
/qapi/qapi-introspect.[ch]
|
qapi: Generate separate .h, .c for each module
Our qapi-schema.json is composed of modules connected by include
directives, but the generated code is monolithic all the same: one
qapi-types.h with all the types, one qapi-visit.h with all the
visitors, and so forth. These monolithic headers get included all
over the place. In my "build everything" tree, adding a QAPI type
recompiles about 4800 out of 5100 objects.
We wouldn't write such monolithic headers by hand. It stands to
reason that we shouldn't generate them, either.
Split up generated qapi-types.h to mirror the schema's modular
structure: one header per module. Name the main module's header
qapi-types.h, and sub-module D/B.json's header D/qapi-types-B.h.
Mirror the schema's includes in the headers, so that qapi-types.h gets
you everything exactly as before. If you need less, you can include
one or more of the sub-module headers. To be exploited shortly.
Split up qapi-types.c, qapi-visit.h, qapi-visit.c, qmp-commands.h,
qmp-commands.c, qapi-event.h, qapi-event.c the same way.
qmp-introspect.h, qmp-introspect.c and qapi.texi remain monolithic.
The split of qmp-commands.c duplicates static helper function
qmp_marshal_output_str() in qapi-commands-char.c and
qapi-commands-misc.c. This happens when commands returning the same
type occur in multiple modules. Not worth avoiding.
Since I'm going to rename qapi-event.[ch] to qapi-events.[ch], and
qmp-commands.[ch] to qapi-commands.[ch], name the shards that way
already, to reduce churn. This requires temporary hacks in
commands.py and events.py. Similarly, c_name() must temporarily
be taught to munge '/' in common.py. They'll go away with the rename.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20180211093607.27351-23-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
[eblake: declare a dummy variable in each .c file, to shut up OSX
toolchain warnings about empty .o files, including hacking c_name()]
Signed-off-by: Eric Blake <eblake@redhat.com>
2018-02-11 12:36:00 +03:00
|
|
|
/qapi/qapi-types-block-core.[ch]
|
|
|
|
|
/qapi/qapi-types-block.[ch]
|
|
|
|
|
/qapi/qapi-types-char.[ch]
|
|
|
|
|
/qapi/qapi-types-common.[ch]
|
|
|
|
|
/qapi/qapi-types-crypto.[ch]
|
|
|
|
|
/qapi/qapi-types-introspect.[ch]
|
|
|
|
|
/qapi/qapi-types-migration.[ch]
|
2018-02-27 02:13:27 +03:00
|
|
|
/qapi/qapi-types-misc.[ch]
|
qapi: Generate separate .h, .c for each module
Our qapi-schema.json is composed of modules connected by include
directives, but the generated code is monolithic all the same: one
qapi-types.h with all the types, one qapi-visit.h with all the
visitors, and so forth. These monolithic headers get included all
over the place. In my "build everything" tree, adding a QAPI type
recompiles about 4800 out of 5100 objects.
We wouldn't write such monolithic headers by hand. It stands to
reason that we shouldn't generate them, either.
Split up generated qapi-types.h to mirror the schema's modular
structure: one header per module. Name the main module's header
qapi-types.h, and sub-module D/B.json's header D/qapi-types-B.h.
Mirror the schema's includes in the headers, so that qapi-types.h gets
you everything exactly as before. If you need less, you can include
one or more of the sub-module headers. To be exploited shortly.
Split up qapi-types.c, qapi-visit.h, qapi-visit.c, qmp-commands.h,
qmp-commands.c, qapi-event.h, qapi-event.c the same way.
qmp-introspect.h, qmp-introspect.c and qapi.texi remain monolithic.
The split of qmp-commands.c duplicates static helper function
qmp_marshal_output_str() in qapi-commands-char.c and
qapi-commands-misc.c. This happens when commands returning the same
type occur in multiple modules. Not worth avoiding.
Since I'm going to rename qapi-event.[ch] to qapi-events.[ch], and
qmp-commands.[ch] to qapi-commands.[ch], name the shards that way
already, to reduce churn. This requires temporary hacks in
commands.py and events.py. Similarly, c_name() must temporarily
be taught to munge '/' in common.py. They'll go away with the rename.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20180211093607.27351-23-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
[eblake: declare a dummy variable in each .c file, to shut up OSX
toolchain warnings about empty .o files, including hacking c_name()]
Signed-off-by: Eric Blake <eblake@redhat.com>
2018-02-11 12:36:00 +03:00
|
|
|
/qapi/qapi-types-net.[ch]
|
|
|
|
|
/qapi/qapi-types-rocker.[ch]
|
|
|
|
|
/qapi/qapi-types-run-state.[ch]
|
|
|
|
|
/qapi/qapi-types-sockets.[ch]
|
|
|
|
|
/qapi/qapi-types-tpm.[ch]
|
|
|
|
|
/qapi/qapi-types-trace.[ch]
|
|
|
|
|
/qapi/qapi-types-transaction.[ch]
|
|
|
|
|
/qapi/qapi-types-ui.[ch]
|
2018-02-11 12:36:05 +03:00
|
|
|
/qapi/qapi-types.[ch]
|
qapi: Generate separate .h, .c for each module
Our qapi-schema.json is composed of modules connected by include
directives, but the generated code is monolithic all the same: one
qapi-types.h with all the types, one qapi-visit.h with all the
visitors, and so forth. These monolithic headers get included all
over the place. In my "build everything" tree, adding a QAPI type
recompiles about 4800 out of 5100 objects.
We wouldn't write such monolithic headers by hand. It stands to
reason that we shouldn't generate them, either.
Split up generated qapi-types.h to mirror the schema's modular
structure: one header per module. Name the main module's header
qapi-types.h, and sub-module D/B.json's header D/qapi-types-B.h.
Mirror the schema's includes in the headers, so that qapi-types.h gets
you everything exactly as before. If you need less, you can include
one or more of the sub-module headers. To be exploited shortly.
Split up qapi-types.c, qapi-visit.h, qapi-visit.c, qmp-commands.h,
qmp-commands.c, qapi-event.h, qapi-event.c the same way.
qmp-introspect.h, qmp-introspect.c and qapi.texi remain monolithic.
The split of qmp-commands.c duplicates static helper function
qmp_marshal_output_str() in qapi-commands-char.c and
qapi-commands-misc.c. This happens when commands returning the same
type occur in multiple modules. Not worth avoiding.
Since I'm going to rename qapi-event.[ch] to qapi-events.[ch], and
qmp-commands.[ch] to qapi-commands.[ch], name the shards that way
already, to reduce churn. This requires temporary hacks in
commands.py and events.py. Similarly, c_name() must temporarily
be taught to munge '/' in common.py. They'll go away with the rename.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20180211093607.27351-23-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
[eblake: declare a dummy variable in each .c file, to shut up OSX
toolchain warnings about empty .o files, including hacking c_name()]
Signed-off-by: Eric Blake <eblake@redhat.com>
2018-02-11 12:36:00 +03:00
|
|
|
/qapi/qapi-visit-block-core.[ch]
|
|
|
|
|
/qapi/qapi-visit-block.[ch]
|
|
|
|
|
/qapi/qapi-visit-char.[ch]
|
|
|
|
|
/qapi/qapi-visit-common.[ch]
|
|
|
|
|
/qapi/qapi-visit-crypto.[ch]
|
|
|
|
|
/qapi/qapi-visit-introspect.[ch]
|
|
|
|
|
/qapi/qapi-visit-migration.[ch]
|
2018-02-27 02:13:27 +03:00
|
|
|
/qapi/qapi-visit-misc.[ch]
|
qapi: Generate separate .h, .c for each module
Our qapi-schema.json is composed of modules connected by include
directives, but the generated code is monolithic all the same: one
qapi-types.h with all the types, one qapi-visit.h with all the
visitors, and so forth. These monolithic headers get included all
over the place. In my "build everything" tree, adding a QAPI type
recompiles about 4800 out of 5100 objects.
We wouldn't write such monolithic headers by hand. It stands to
reason that we shouldn't generate them, either.
Split up generated qapi-types.h to mirror the schema's modular
structure: one header per module. Name the main module's header
qapi-types.h, and sub-module D/B.json's header D/qapi-types-B.h.
Mirror the schema's includes in the headers, so that qapi-types.h gets
you everything exactly as before. If you need less, you can include
one or more of the sub-module headers. To be exploited shortly.
Split up qapi-types.c, qapi-visit.h, qapi-visit.c, qmp-commands.h,
qmp-commands.c, qapi-event.h, qapi-event.c the same way.
qmp-introspect.h, qmp-introspect.c and qapi.texi remain monolithic.
The split of qmp-commands.c duplicates static helper function
qmp_marshal_output_str() in qapi-commands-char.c and
qapi-commands-misc.c. This happens when commands returning the same
type occur in multiple modules. Not worth avoiding.
Since I'm going to rename qapi-event.[ch] to qapi-events.[ch], and
qmp-commands.[ch] to qapi-commands.[ch], name the shards that way
already, to reduce churn. This requires temporary hacks in
commands.py and events.py. Similarly, c_name() must temporarily
be taught to munge '/' in common.py. They'll go away with the rename.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <20180211093607.27351-23-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
[eblake: declare a dummy variable in each .c file, to shut up OSX
toolchain warnings about empty .o files, including hacking c_name()]
Signed-off-by: Eric Blake <eblake@redhat.com>
2018-02-11 12:36:00 +03:00
|
|
|
/qapi/qapi-visit-net.[ch]
|
|
|
|
|
/qapi/qapi-visit-rocker.[ch]
|
|
|
|
|
/qapi/qapi-visit-run-state.[ch]
|
|
|
|
|
/qapi/qapi-visit-sockets.[ch]
|
|
|
|
|
/qapi/qapi-visit-tpm.[ch]
|
|
|
|
|
/qapi/qapi-visit-trace.[ch]
|
|
|
|
|
/qapi/qapi-visit-transaction.[ch]
|
|
|
|
|
/qapi/qapi-visit-ui.[ch]
|
2018-02-11 12:36:05 +03:00
|
|
|
/qapi/qapi-visit.[ch]
|
|
|
|
|
/qapi/qapi-doc.texi
|
gitignore: anchor all ignored names
by default, patterns/names in .gitignore are applied
recursively to all subdirectories. So any name mentioned
in .gitignore is ignored in all subdirectores. This is good
for, say. object files (*.o), but not good for particular
names which should be ignored only in one directory. For
example, qemu-img.1 file is generated in the top directory,
and it should be ignored only there, not in some subdir.
At first, this might not matter much, but we have lots of
examples already where it actually does not help at all.
For example, top-level .gitignore ignores a file/dir named
"patches" (which is very questionable by itself), but it
is applied recursively, so git also ignores, for example,
debian/patches/ which should not be ignored.
So anchor all the names where appropriate. .gitignore
should be cleaned up further, which will be addressed in
a subsequent patch.
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
2014-02-11 14:22:32 +04:00
|
|
|
/qemu-doc.html
|
|
|
|
|
/qemu-doc.info
|
2017-01-13 17:41:34 +03:00
|
|
|
/qemu-doc.txt
|
gitignore: anchor all ignored names
by default, patterns/names in .gitignore are applied
recursively to all subdirectories. So any name mentioned
in .gitignore is ignored in all subdirectores. This is good
for, say. object files (*.o), but not good for particular
names which should be ignored only in one directory. For
example, qemu-img.1 file is generated in the top directory,
and it should be ignored only there, not in some subdir.
At first, this might not matter much, but we have lots of
examples already where it actually does not help at all.
For example, top-level .gitignore ignores a file/dir named
"patches" (which is very questionable by itself), but it
is applied recursively, so git also ignores, for example,
debian/patches/ which should not be ignored.
So anchor all the names where appropriate. .gitignore
should be cleaned up further, which will be addressed in
a subsequent patch.
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
2014-02-11 14:22:32 +04:00
|
|
|
/qemu-img
|
|
|
|
|
/qemu-nbd
|
|
|
|
|
/qemu-options.def
|
|
|
|
|
/qemu-options.texi
|
|
|
|
|
/qemu-img-cmds.texi
|
|
|
|
|
/qemu-img-cmds.h
|
|
|
|
|
/qemu-io
|
|
|
|
|
/qemu-ga
|
|
|
|
|
/qemu-bridge-helper
|
2017-10-20 10:09:14 +03:00
|
|
|
/qemu-keymap
|
gitignore: anchor all ignored names
by default, patterns/names in .gitignore are applied
recursively to all subdirectories. So any name mentioned
in .gitignore is ignored in all subdirectores. This is good
for, say. object files (*.o), but not good for particular
names which should be ignored only in one directory. For
example, qemu-img.1 file is generated in the top directory,
and it should be ignored only there, not in some subdir.
At first, this might not matter much, but we have lots of
examples already where it actually does not help at all.
For example, top-level .gitignore ignores a file/dir named
"patches" (which is very questionable by itself), but it
is applied recursively, so git also ignores, for example,
debian/patches/ which should not be ignored.
So anchor all the names where appropriate. .gitignore
should be cleaned up further, which will be addressed in
a subsequent patch.
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
2014-02-11 14:22:32 +04:00
|
|
|
/qemu-monitor.texi
|
2015-09-10 18:39:01 +03:00
|
|
|
/qemu-monitor-info.texi
|
2016-06-08 23:26:59 +03:00
|
|
|
/qemu-version.h
|
|
|
|
|
/qemu-version.h.tmp
|
2016-09-23 12:16:06 +03:00
|
|
|
/module_block.h
|
2017-09-26 18:14:21 +03:00
|
|
|
/scsi/qemu-pr-helper
|
2017-03-02 21:25:52 +03:00
|
|
|
/vhost-user-scsi
|
2018-01-04 04:53:34 +03:00
|
|
|
/vhost-user-blk
|
gitignore: anchor all ignored names
by default, patterns/names in .gitignore are applied
recursively to all subdirectories. So any name mentioned
in .gitignore is ignored in all subdirectores. This is good
for, say. object files (*.o), but not good for particular
names which should be ignored only in one directory. For
example, qemu-img.1 file is generated in the top directory,
and it should be ignored only there, not in some subdir.
At first, this might not matter much, but we have lots of
examples already where it actually does not help at all.
For example, top-level .gitignore ignores a file/dir named
"patches" (which is very questionable by itself), but it
is applied recursively, so git also ignores, for example,
debian/patches/ which should not be ignored.
So anchor all the names where appropriate. .gitignore
should be cleaned up further, which will be addressed in
a subsequent patch.
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
2014-02-11 14:22:32 +04:00
|
|
|
/fsdev/virtfs-proxy-helper
|
2017-09-05 05:11:50 +03:00
|
|
|
*.tmp
|
2015-03-20 19:30:44 +03:00
|
|
|
*.[1-9]
|
2008-09-09 21:15:28 +04:00
|
|
|
*.a
|
|
|
|
|
*.aux
|
|
|
|
|
*.cp
|
|
|
|
|
*.exe
|
2015-07-29 20:10:50 +03:00
|
|
|
*.msi
|
2014-02-10 10:48:56 +04:00
|
|
|
*.dll
|
|
|
|
|
*.so
|
|
|
|
|
*.mo
|
2008-09-09 21:15:28 +04:00
|
|
|
*.fn
|
|
|
|
|
*.ky
|
|
|
|
|
*.log
|
2010-01-30 01:16:50 +03:00
|
|
|
*.pdf
|
2015-03-20 19:30:44 +03:00
|
|
|
*.pod
|
2011-04-13 10:42:16 +04:00
|
|
|
*.cps
|
|
|
|
|
*.fns
|
|
|
|
|
*.kys
|
2008-09-09 21:15:28 +04:00
|
|
|
*.pg
|
2010-05-22 22:24:51 +04:00
|
|
|
*.pyc
|
2008-09-09 21:15:28 +04:00
|
|
|
*.toc
|
|
|
|
|
*.tp
|
|
|
|
|
*.vr
|
|
|
|
|
*.d
|
gitignore: anchor all ignored names
by default, patterns/names in .gitignore are applied
recursively to all subdirectories. So any name mentioned
in .gitignore is ignored in all subdirectores. This is good
for, say. object files (*.o), but not good for particular
names which should be ignored only in one directory. For
example, qemu-img.1 file is generated in the top directory,
and it should be ignored only there, not in some subdir.
At first, this might not matter much, but we have lots of
examples already where it actually does not help at all.
For example, top-level .gitignore ignores a file/dir named
"patches" (which is very questionable by itself), but it
is applied recursively, so git also ignores, for example,
debian/patches/ which should not be ignored.
So anchor all the names where appropriate. .gitignore
should be cleaned up further, which will be addressed in
a subsequent patch.
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
2014-02-11 14:22:32 +04:00
|
|
|
!/scripts/qemu-guest-agent/fsfreeze-hook.d
|
2009-01-22 20:15:25 +03:00
|
|
|
*.o
|
2013-08-07 19:40:03 +04:00
|
|
|
.sdk
|
2013-03-22 12:44:13 +04:00
|
|
|
*.gcda
|
|
|
|
|
*.gcno
|
gitignore: anchor all ignored names
by default, patterns/names in .gitignore are applied
recursively to all subdirectories. So any name mentioned
in .gitignore is ignored in all subdirectores. This is good
for, say. object files (*.o), but not good for particular
names which should be ignored only in one directory. For
example, qemu-img.1 file is generated in the top directory,
and it should be ignored only there, not in some subdir.
At first, this might not matter much, but we have lots of
examples already where it actually does not help at all.
For example, top-level .gitignore ignores a file/dir named
"patches" (which is very questionable by itself), but it
is applied recursively, so git also ignores, for example,
debian/patches/ which should not be ignored.
So anchor all the names where appropriate. .gitignore
should be cleaned up further, which will be addressed in
a subsequent patch.
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
2014-02-11 14:22:32 +04:00
|
|
|
/pc-bios/bios-pq/status
|
|
|
|
|
/pc-bios/vgabios-pq/status
|
|
|
|
|
/pc-bios/optionrom/linuxboot.asm
|
|
|
|
|
/pc-bios/optionrom/linuxboot.bin
|
|
|
|
|
/pc-bios/optionrom/linuxboot.raw
|
|
|
|
|
/pc-bios/optionrom/linuxboot.img
|
2016-05-23 21:11:33 +03:00
|
|
|
/pc-bios/optionrom/linuxboot_dma.asm
|
|
|
|
|
/pc-bios/optionrom/linuxboot_dma.bin
|
|
|
|
|
/pc-bios/optionrom/linuxboot_dma.raw
|
|
|
|
|
/pc-bios/optionrom/linuxboot_dma.img
|
gitignore: anchor all ignored names
by default, patterns/names in .gitignore are applied
recursively to all subdirectories. So any name mentioned
in .gitignore is ignored in all subdirectores. This is good
for, say. object files (*.o), but not good for particular
names which should be ignored only in one directory. For
example, qemu-img.1 file is generated in the top directory,
and it should be ignored only there, not in some subdir.
At first, this might not matter much, but we have lots of
examples already where it actually does not help at all.
For example, top-level .gitignore ignores a file/dir named
"patches" (which is very questionable by itself), but it
is applied recursively, so git also ignores, for example,
debian/patches/ which should not be ignored.
So anchor all the names where appropriate. .gitignore
should be cleaned up further, which will be addressed in
a subsequent patch.
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
2014-02-11 14:22:32 +04:00
|
|
|
/pc-bios/optionrom/multiboot.asm
|
|
|
|
|
/pc-bios/optionrom/multiboot.bin
|
|
|
|
|
/pc-bios/optionrom/multiboot.raw
|
|
|
|
|
/pc-bios/optionrom/multiboot.img
|
|
|
|
|
/pc-bios/optionrom/kvmvapic.asm
|
|
|
|
|
/pc-bios/optionrom/kvmvapic.bin
|
|
|
|
|
/pc-bios/optionrom/kvmvapic.raw
|
|
|
|
|
/pc-bios/optionrom/kvmvapic.img
|
|
|
|
|
/pc-bios/s390-ccw/s390-ccw.elf
|
|
|
|
|
/pc-bios/s390-ccw/s390-ccw.img
|
2017-06-06 17:55:19 +03:00
|
|
|
/docs/interop/qemu-ga-qapi.texi
|
|
|
|
|
/docs/interop/qemu-ga-ref.html
|
|
|
|
|
/docs/interop/qemu-ga-ref.info*
|
|
|
|
|
/docs/interop/qemu-ga-ref.txt
|
|
|
|
|
/docs/interop/qemu-qmp-qapi.texi
|
|
|
|
|
/docs/interop/qemu-qmp-ref.html
|
|
|
|
|
/docs/interop/qemu-qmp-ref.info*
|
|
|
|
|
/docs/interop/qemu-qmp-ref.txt
|
2017-03-15 15:56:56 +03:00
|
|
|
/docs/version.texi
|
2017-01-13 17:41:35 +03:00
|
|
|
*.tps
|
2009-01-22 20:15:25 +03:00
|
|
|
.stgit-*
|
2017-09-29 13:11:56 +03:00
|
|
|
.git-submodule-status
|
2010-07-23 09:59:52 +04:00
|
|
|
cscope.*
|
2011-01-31 18:20:40 +03:00
|
|
|
tags
|
2011-02-24 08:34:59 +03:00
|
|
|
TAGS
|
2016-06-01 12:21:24 +03:00
|
|
|
docker-src.*
|
2011-02-24 08:34:59 +03:00
|
|
|
*~
|
2017-07-18 07:55:31 +03:00
|
|
|
*.ast_raw
|
|
|
|
|
*.depend_raw
|
2017-01-25 19:14:15 +03:00
|
|
|
trace.h
|
|
|
|
|
trace.c
|
|
|
|
|
trace-ust.h
|
|
|
|
|
trace-ust.h
|
|
|
|
|
trace-dtrace.h
|
|
|
|
|
trace-dtrace.dtrace
|
|
|
|
|
trace-root.h
|
|
|
|
|
trace-root.c
|
|
|
|
|
trace-ust-root.h
|
|
|
|
|
trace-ust-root.h
|
|
|
|
|
trace-ust-all.h
|
|
|
|
|
trace-ust-all.c
|
|
|
|
|
trace-dtrace-root.h
|
|
|
|
|
trace-dtrace-root.dtrace
|
|
|
|
|
trace-ust-all.h
|
|
|
|
|
trace-ust-all.c
|