Jonathon Jongsma 1450bb4ddb Be explicit about spice-common license ... Use same license as spice-gtk and spice modules (LGPL 2.1) since those licenses applied to the spice-common submodule in the past. This makes it more clear that if you use spice-common separately, the license is still LGPL. Also mention license and copyright in generated files.		2013-10-23 11:41:43 -05:00
build-aux	build-sys: make it a seperately buildable spice-common library	2012-03-22 20:21:05 +01:00
common	ssl: Don't try hostname check if cert subject check fails	2013-10-11 10:21:54 +02:00
m4	build-sys: make it a seperately buildable spice-common library	2012-03-22 20:21:05 +01:00
python_modules	codegen: Add a --generate-wireshark-dissector option	2013-10-23 11:41:43 -05:00
spice-protocol@8b436f8a3e	Remove INLINE usage	2013-10-04 12:45:00 +02:00
.gitmodules	build-sys: make it a seperately buildable spice-common library	2012-03-22 20:21:05 +01:00
autogen.sh	build-sys: make it a seperately buildable spice-common library	2012-03-22 20:21:05 +01:00
configure.ac	build-sys: add --enable-smartcard=auto	2013-09-26 19:03:31 +02:00
COPYING	Be explicit about spice-common license	2013-10-23 11:41:43 -05:00
git.mk	Update git.mk to latest version	2012-09-21 10:51:17 +02:00
Makefile.am	spice-common: don't install spice-protocol	2012-08-09 12:44:41 +02:00
spice1.proto	support seamless migration	2012-08-27 09:06:26 +03:00
spice_codegen.py	Be explicit about spice-common license	2013-10-23 11:41:43 -05:00
spice.proto	proto: add fake last message in base channel	2013-09-12 13:49:25 +02:00