On 05/11/2016 04:16 AM, Michal Privoznik wrote:
On 10.05.2016 17:58, Cole Robinson wrote:
On 05/10/2016 11:56 AM, Michal Privoznik wrote:
On 10.05.2016 17:23, Ján Tomko wrote:
On Mon, May 09, 2016 at 02:21:53PM +0200, poma wrote:
libvirt/qemu.conf: spaces correction
--- src/qemu/qemu.conf | 42 +++++++++++++++++++++--------------------- 1 file changed, 21 insertions(+), 21 deletions(-)
@@ -285,11 +285,11 @@
# The default format for Qemu/KVM guest save images is raw; that is, the -# memory from the domain is dumped out directly to a file. If you have +# memory from the domain is dumped out directly to a file. If you have # guests with a large amount of memory, however, this can take up quite -# a bit of space. If you would like to compress the images while they +# a bit of space. If you would like to compress the images while they # are being saved to disk, you can also set "lzop", "gzip", "bzip2", or "xz" -# for save_image_format. Note that this means you slow down the process of +# for save_image_format. Note that this means you slow down the process of # saving a domain in order to save disk space; the list above is in descending # order by performance and ascending order by compression ratio. #
Most of the changes remove double spacing between sentences. This was intentional and I do not think it needs to be corrected.
Can you elaborate more on the reasoning behind this intent?
What I grasped from the article is that double spacing is now being slowly deprecated in favour of a single space between both words and sentences.
Double spacing is certainly less common in 'the real world' but it seems like there are a disproportionate number of people who use it in open source communication. Still a minority though, and I agree with the general idea of standardizing on single space in libvirt code - Cole