External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-07-12 12:55:46 +00:00
Code Issues Packages Projects Releases Wiki Activity
8da7520d22
libvirt/tests/virnetdaemondata
History
Erik Skultety 8da7520d22 tests: virnetdaemon: Replace tabs with spaces 
We already did this once, but somehow commit 252610f7 managed to bring the tabs
back again.

Signed-off-by: Erik Skultety <eskultet@redhat.com>
2016-04-21 12:36:03 +02:00
..
input-data-admin-nomdns.json test: Replace tabs with spaces in virnetdaemondata json files 2015-08-24 09:30:40 +02:00
input-data-admin-server-names.json tests: virnetdaemon: Replace tabs with spaces 2016-04-21 12:36:03 +02:00
input-data-anon-clients.json tests: Adapt virnetservertest to daemon refactor 2015-06-16 13:46:20 +02:00
input-data-initial-nomdns.json tests: Adapt virnetservertest to daemon refactor 2015-06-16 13:46:20 +02:00
input-data-initial.json tests: Adapt virnetservertest to daemon refactor 2015-06-16 13:46:20 +02:00
input-data-no-keepalive-required.json test: Replace tabs with spaces in virnetdaemondata json files 2015-08-24 09:30:40 +02:00
output-data-admin-nomdns.json virnetdaemon: Store servers in a hash table 2016-02-17 12:46:34 +01:00
output-data-admin-server-names.json virnetdaemon: Store servers in a hash table 2016-02-17 12:46:34 +01:00
output-data-anon-clients.json virnetdaemon: Store servers in a hash table 2016-02-17 12:46:34 +01:00
output-data-initial-nomdns.json virnetdaemon: Store servers in a hash table 2016-02-17 12:46:34 +01:00
output-data-initial.json virnetdaemon: Store servers in a hash table 2016-02-17 12:46:34 +01:00
output-data-no-keepalive-required.json tests: virnetdaemon: Replace tabs with spaces 2016-04-21 12:36:03 +02:00
README tests: Adapt virnetservertest to daemon refactor 2015-06-16 13:46:20 +02:00

README 

   virnetservertest data files
   ===========================

The various input-data-*.json files are a record of all the historical
formats that libvirt has been able to produce data for. Everytime a
new field is added to the JSON output, a *new* input data file should
be created. We must not add new fields to existing input-data files,
nor must we ever re-structure them if code changes, as we must check
new code handles the legacy formats.

The various output-data-*.json files are the record of what the *new*
JSON output should look like for the correspondingly named input-data
file. It is permissible to change the existing output-data-*.json
files if the format we save in is updated.