1. 18 1月, 2019 14 次提交
  2. 17 1月, 2019 2 次提交
  3. 15 1月, 2019 1 次提交
  4. 10 1月, 2019 1 次提交
  5. 19 12月, 2018 1 次提交
  6. 14 12月, 2018 1 次提交
    • D
      Remove all Author(s): lines from source file headers · 60046283
      Daniel P. Berrangé 提交于
      In many files there are header comments that contain an Author:
      statement, supposedly reflecting who originally wrote the code.
      In a large collaborative project like libvirt, any non-trivial
      file will have been modified by a large number of different
      contributors. IOW, the Author: comments are quickly out of date,
      omitting people who have made significant contribitions.
      
      In some places Author: lines have been added despite the person
      merely being responsible for creating the file by moving existing
      code out of another file. IOW, the Author: lines give an incorrect
      record of authorship.
      
      With this all in mind, the comments are useless as a means to identify
      who to talk to about code in a particular file. Contributors will always
      be better off using 'git log' and 'git blame' if they need to  find the
      author of a particular bit of code.
      
      This commit thus deletes all Author: comments from the source and adds
      a rule to prevent them reappearing.
      
      The Copyright headers are similarly misleading and inaccurate, however,
      we cannot delete these as they have legal meaning, despite being largely
      inaccurate. In addition only the copyright holder is permitted to change
      their respective copyright statement.
      Reviewed-by: NErik Skultety <eskultet@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      60046283
  7. 20 11月, 2018 1 次提交
  8. 16 11月, 2018 1 次提交
  9. 08 10月, 2018 1 次提交
  10. 27 9月, 2018 1 次提交
  11. 20 9月, 2018 1 次提交
  12. 18 9月, 2018 1 次提交
  13. 13 9月, 2018 1 次提交
  14. 12 6月, 2018 1 次提交
    • J
      qemu: fix uninitialised variable in virQEMUDriverConfigLoadFile · bf72ab16
      Julio Faracco 提交于
      Since virConfGetValueBool() can return earlier, the parameter 'value'
      might be not initialised properly inside this method. Another proof:
      Valgrind is returning this error during the libvirtd daemon startup:
      
      ==16199== Conditional jump or move depends on uninitialised value(s)
      ==16199==    at 0x27FFFEF4: virQEMUDriverConfigLoadFile (qemu_conf.c:809)
      ==16199==    by 0x2807665C: qemuStateInitialize (qemu_driver.c:654)
      ==16199==    by 0x5535428: virStateInitialize (libvirt.c:662)
      ==16199==    by 0x12AED8: daemonRunStateInit (remote_daemon.c:802)
      ==16199==    by 0x536DE18: virThreadHelper (virthread.c:206)
      ==16199==    by 0x6CB36DA: start_thread (pthread_create.c:463)
      ==16199==    by 0x6FEC88E: clone (clone.S:95)
      Signed-off-by: NJulio Faracco <jcfaracco@gmail.com>
      Reviewed-by: NJán Tomko <jtomko@redhat.com>
      Signed-off-by: NJán Tomko <jtomko@redhat.com>
      bf72ab16
  15. 08 6月, 2018 1 次提交
  16. 06 6月, 2018 2 次提交
  17. 05 6月, 2018 1 次提交
  18. 11 5月, 2018 1 次提交
  19. 18 4月, 2018 1 次提交
    • M
      virobject: Introduce VIR_CLASS_NEW() macro · 10f94828
      Michal Privoznik 提交于
      So far we are repeating the following lines over and over:
      
        if (!(virSomeObjectClass = virClassNew(virClassForObject(),
                                   "virSomeObject",
                                   sizeof(virSomeObject),
                                   virSomeObjectDispose)))
            return -1;
      
      While this works, it is impossible to do some checking. Firstly,
      the class name (the 2nd argument) doesn't match the name in the
      code in all cases (the 3rd argument). Secondly, the current style
      is needlessly verbose. This commit turns example into following:
      
        if (!(VIR_CLASS_NEW(virSomeObject,
                            virClassForObject)))
            return -1;
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      Reviewed-by: NDaniel P. Berrangé <berrange@redhat.com>
      10f94828
  20. 19 2月, 2018 1 次提交
  21. 12 2月, 2018 1 次提交
  22. 02 2月, 2018 1 次提交
  23. 08 11月, 2017 1 次提交
  24. 07 11月, 2017 2 次提交