qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amarjargal Gundjalam <amarjargal16@gmail.com>
To: "Volker Rümelin" <vr_qemu@t-online.de>
Cc: "Gerd Hoffmann" <kraxel@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Thomas Huth" <thuth@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH v3 2/4] hw/audio: fix tab indentation
Date: Tue, 25 Oct 2022 22:32:11 +0800	[thread overview]
Message-ID: <0848444f-1940-329d-9e3d-0b6b86cf36c6@gmail.com> (raw)
In-Reply-To: <407d964d-7a00-4e94-a0d7-054eb6f881cf@gmail.com>


On 24/10/22 23:42, Amarjargal Gundjalam wrote:
>
> On 23/10/22 15:53, Volker Rümelin wrote:
>> Am 21.10.22 um 18:59 schrieb Amarjargal Gundjalam:
>>
>>> The TABs should be replaced with spaces, to make sure that we have a
>>> consistent coding style with an indentation of 4 spaces everywhere.
>>>
>>> Resolves:https://gitlab.com/qemu-project/qemu/-/issues/370
>>> Reviewed-by: Daniel P. Berrangé<berrange@redhat.com>
>>>
>>> Signed-off-by: Amarjargal Gundjalam<amarjargal16@gmail.com>
>>> ---
>>>   hw/audio/fmopl.c          | 1664 
>>> ++++++++++++++++++-------------------
>>>   hw/audio/fmopl.h          |  138 +--
>>>   hw/audio/intel-hda-defs.h | 1008 +++++++++++-----------
>>>   hw/audio/wm8750.c         |  270 +++---
>>>   4 files changed, 1540 insertions(+), 1540 deletions(-)
>>
>> Hi Amarjargal,
>>
>> I had a look at hw/audio/fmopl.c and I think the result doesn't look 
>> right. A few comments are no longer correctly aligned. I guess you 
>> just replaced all TABs with four spaces. But this is not how TABs work.
>>
>> For reference: I used the vim command
>>
>> :%s/^I/    /g
>>
>> and the result is identical to your file. The commands
>>
>> :se ts=4 expandtab
>> :retab
>>
>> would have been a much better starting point for the last few manual 
>> changes.
>>
>> Here is another example. For the file hw/audio/wm8750.c I would have 
>> started with the following vim commands
>>
>> :se ts=8 expandtab
>> :retab
>>
>> With best regards,
>> Volker
>
> Hi Volker,
>
> Thank you for your review!
>
> Yes, I did indeed replaced all the tabs with spaces. I'll fix all of 
> them and update.
>
> Best Regards,
>
> Amarjargal
>
>
Hello again,

I redid the whole thing with vim retab and sent a new version of the 
patches. I hope they're alright this time.

Thank you,

Amarjargal



  reply	other threads:[~2022-10-25 14:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21 16:59 [PATCH v3 0/4] ui:hw: fix tab indentation Amarjargal Gundjalam
2022-10-21 16:59 ` [PATCH v3 1/4] ui: " Amarjargal Gundjalam
2022-10-21 16:59 ` [PATCH v3 2/4] hw/audio: " Amarjargal Gundjalam
2022-10-23  7:53   ` Volker Rümelin
2022-10-24 15:42     ` Amarjargal Gundjalam
2022-10-25 14:32       ` Amarjargal Gundjalam [this message]
2022-10-21 16:59 ` [PATCH v3 3/4] hw/display: " Amarjargal Gundjalam
2022-10-21 16:59 ` [PATCH v3 4/4] hw/usb: " Amarjargal Gundjalam

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=0848444f-1940-329d-9e3d-0b6b86cf36c6@gmail.com \
    --to=amarjargal16@gmail.com \
    --cc=berrange@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=vr_qemu@t-online.de \
    /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).