xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Elena Ufimtseva <ufimtseva@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Keir Fraser <keir@xen.org>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	George Dunlap <george.dunlap@eu.citrix.com>,
	Dario Faggioli <dario.faggioli@citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] numa.c: use spaces instead of tabs
Date: Wed, 3 Sep 2014 08:34:05 -0400	[thread overview]
Message-ID: <CAEr7rXiCiaXJgHDtkyQ_Hur86KDfnOXHTJrGTLvvSdwLZW65iA@mail.gmail.com> (raw)
In-Reply-To: <540725DE0200007800030453@mail.emea.novell.com>

On Wed, Sep 3, 2014 at 8:29 AM, Jan Beulich <JBeulich@suse.com> wrote:
>>>> On 03.09.14 at 13:59, <ufimtseva@gmail.com> wrote:
>> Jan, you say that such style is not used.. But numa.c uses tabs as
>> :set list shows and its not Xen style either.
>> Coding style says - 4 spaces for one level of indent. numa.c uses tabs
>> and sometimes space between tabs.
>>
>> I am looking at the rest of the files in xen/arch/x86/ and see that
>> they have all same tab= 4 spaces for indentation.
>> for example see xen/arch/x86/domain.c.
>> I used this for vim to re-tab the file: set noai ts=4 sw=8 expandtab
>>
>> Linux has 8 spaces for tabs.. So I am lost here.
>
> In a few files, original Linux style got retained, and we're accepting
> that. See for example xen/arch/x86/cpu/. As a result, keeping the
> file here as is would be fine (as indicated before); the only alternative
> would be to fully switch it to Xen style.
>
> Jan
>

Jan

I understand that, but that style is mixed. Not linux, not Xen :)
And tabs also do not make it look like linux.
But I got your point I think. Or leave it as it is (with tabs), or
change it to Xen style.

-- 
Elena

  reply	other threads:[~2014-09-03 12:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-03  4:18 [PATCH] numa.c: use spaces instead of tabs Elena Ufimtseva
2014-09-03  9:52 ` Dario Faggioli
2014-09-03 10:01   ` Jan Beulich
2014-09-03 11:59     ` Elena Ufimtseva
2014-09-03 12:18       ` Ian Campbell
2014-09-03 12:29         ` Elena Ufimtseva
2014-09-03 12:29       ` Jan Beulich
2014-09-03 12:34         ` Elena Ufimtseva [this message]
2014-09-03 12:40           ` Jan Beulich
2014-09-06 17:28             ` Don Slutz
2014-09-08  6:53               ` Jan Beulich

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=CAEr7rXiCiaXJgHDtkyQ_Hur86KDfnOXHTJrGTLvvSdwLZW65iA@mail.gmail.com \
    --to=ufimtseva@gmail.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=dario.faggioli@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=keir@xen.org \
    --cc=xen-devel@lists.xen.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).