From: Kevin Wolf <mail@kevin-wolf.de>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] [PATCH] qemu-io: Verify read data by patterns
Date: Thu, 9 Apr 2009 20:55:07 +0200 [thread overview]
Message-ID: <200904092055.08042@kevin-wolf.de> (raw)
In-Reply-To: <49DE3641.9090900@codemonkey.ws>
Am Donnerstag, 9. April 2009 19:54 schrieb Anthony Liguori:
> Kevin Wolf wrote:
> > This is what you get for using tabs. You deserve it. ;-)
> >
> > Seriously, I found this really annoying when I did the patch because
> > almost everything else in qemu has four spaces and I needed to change my
> > editor settings for just this file. But I still left indentation on four
> > characters, so this line did fit for me.
> >
> > I can either send a second version of the patch which fixes this line, or
> > we could have a patch which changes the indentation of the whole file to
> > four spaces (as specified in the coding style document). qemu-io might be
> > new enough to not destroy valuable svn blame information with such a
> > patch.
>
> The only reason I merged it as-is is because the code was derived from
> something else. I didn't want to force a reindentation that would make
> it harder to keep the code synced against the upstream project.
That makes sense. However, I'm not sure if there is much left to sync with
upstream? The code structure might be similar to upstream and maybe a few
helper functions are the same (I'm not sure about that), but all in all the
code seems to be pretty much specific to qemu.
So if there are any chances that we actually will merge upstream changes in
future, I'm glad to change that one line. But if this is going to remain a
purely theoretical option, I would prefer to change the indentation.
Kevin
next prev parent reply other threads:[~2009-04-09 18:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 13:46 [Qemu-devel] [PATCH] qemu-io: Verify read data by patterns Kevin Wolf
2009-04-09 15:33 ` Christoph Hellwig
2009-04-09 17:07 ` Kevin Wolf
2009-04-09 17:15 ` Christoph Hellwig
2009-04-09 17:54 ` Anthony Liguori
2009-04-09 18:55 ` Kevin Wolf [this message]
2009-04-10 16:15 ` Christoph Hellwig
2009-04-10 20:23 ` Kevin Wolf
2009-04-10 16:14 ` Christoph Hellwig
2009-04-10 20:18 ` Kevin Wolf
2009-04-12 4:18 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200904092055.08042@kevin-wolf.de \
--to=mail@kevin-wolf.de \
--cc=hch@lst.de \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).