From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] Fix indentation in jit.c
Date: Thu, 12 Dec 2019 19:54:00 -0000 [thread overview]
Message-ID: <41207875-8bea-127d-9b4d-0daa0f50eaa5@polymtl.ca> (raw)
In-Reply-To: <8736dp5pwq.fsf@tromey.com>
On 2019-12-12 2:01 p.m., Tom Tromey wrote:
>>>>>> "Simon" == Simon Marchi <simon.marchi@polymtl.ca> writes:
>
> Simon> Many places in this file use spaces only for indentation. Fix them to
> Simon> conform to GNU style.
>
> Simon> gdb/ChangeLog:
>
> Simon> * jit.c: Fix indentation, replace spaces with tabs where
> Simon> applicable.
>
> Is this really our policy? I thought others (Joel maybe?) had argued
> for no tabs in the past, or that maybe we settled on a "don't care"
> approach.
Hmm I'm confused. Doesn't the GNU style mandate using tabs + spaces for
indentation? Using a tab for whole groups of 8 columns, then completing
with spaces? I have never heard that we would accept spaces only.
Now I can't find the reference in the GNU coding standards, so I am
wondering if I just imagined this all these years.
Simon
next prev parent reply other threads:[~2019-12-12 19:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 6:38 [PATCH 1/2] Replace xmalloc/xfree with vector " Simon Marchi
2019-12-11 6:38 ` [PATCH 2/2] Fix indentation " Simon Marchi
2019-12-12 19:01 ` Tom Tromey
2019-12-12 19:54 ` Simon Marchi [this message]
2019-12-13 9:11 ` Strasuns, Mihails
2019-12-13 9:18 ` Eli Zaretskii
2019-12-13 14:43 ` Pedro Alves
2019-12-13 15:14 ` Simon Marchi
2019-12-12 19:00 ` [PATCH 1/2] Replace xmalloc/xfree with vector " Tom Tromey
2019-12-12 19:55 ` Simon Marchi
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=41207875-8bea-127d-9b4d-0daa0f50eaa5@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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