qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Programmingkid <programmingkidx@gmail.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v8] block/raw-posix.c: Fix raw_getlength() on Mac OS X for CD
Date: Tue, 20 Jan 2015 15:36:38 -0500	[thread overview]
Message-ID: <9B8B78FE-703C-4566-ADA1-3AFE68234E74@gmail.com> (raw)
In-Reply-To: <877fwhryc2.fsf@blackfin.pond.sub.org>


On Jan 20, 2015, at 3:28 PM, Markus Armbruster wrote:

> Programmingkid <programmingkidx@gmail.com> writes:
> 
>> On Jan 20, 2015, at 10:22 AM, Eric Blake wrote:
>> 
>>> On 01/20/2015 07:29 AM, Programmingkid wrote:
>>>> 
>>>> On Jan 20, 2015, at 3:33 AM, Markus Armbruster wrote:
>>>> 
>>>>> Programmingkid <programmingkidx@gmail.com> writes:
>>>>> 
>>>>>> Subject was: 
>>>>>> Re: [PATCH v7] block/raw-posix.c: Fixes raw_getlength() 
>>>>>> on Mac OS X so that it reports the correct length of a real CD
>>>>> 
>>>>> Patch history information goes...
>>> 
>>>>> 
>>>>> ... below the --- divider.
>>>> 
>>>> I thought I did this. The information above is the description of the patch. 
>>>> Not its history.
>>> 
>>> Anything that mentions 'v7' is history.  When you read 'git log', you
>>> will not see mentions of 'v7', because no one cares how many tries it
>>> took to get a patch into git.  Knowing about v7 only matters to the
>>> reviewers of v8, hence it is patch history that belongs after the divider.
>> 
>> Ok. 
>> 
>>> 
>>> 
>>>>>> +
>>>>>> +            if (ioctl(fd, DKIOCGETBLOCKCOUNT, &sectors) == 0
>>>>>> +               && ioctl(fd, DKIOCGETBLOCKSIZE, &sector_size) == 0) {
>>> 
>>> Indentation looks off here.
>> 
>> It does look a little odd, but it also communicates that this is one
>> statement (IMHO).
> 
> It's not how the rest of QEMU is indented.  Please try to blend in :)
> 
> I feel bad about notpicking v8 of an obviously useful and patch that is
> basically just fine except for these little things.  Thanks for
> persevering!

Thanks for your encouragement. I personally would have had that whole if
condition on one line, but others want an 80 line maximum. 

  reply	other threads:[~2015-01-20 20:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-19 22:12 [Qemu-devel] [PATCH v8] block/raw-posix.c: Fix raw_getlength() on Mac OS X for CD Programmingkid
2015-01-20  8:33 ` Markus Armbruster
2015-01-20 14:29   ` Programmingkid
2015-01-20 15:22     ` Eric Blake
2015-01-20 16:08       ` Programmingkid
2015-01-20 20:28         ` Markus Armbruster
2015-01-20 20:36           ` Programmingkid [this message]
2015-01-21  7:54             ` Markus Armbruster
2015-01-21 14:38               ` Programmingkid
2015-01-20 14:46 ` Stefan Hajnoczi
2015-01-20 14:55   ` Peter Maydell
2015-02-06 17:14 ` Kevin Wolf

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=9B8B78FE-703C-4566-ADA1-3AFE68234E74@gmail.com \
    --to=programmingkidx@gmail.com \
    --cc=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).