From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] package: indentation cleanup
Date: Mon, 3 Nov 2014 08:33:36 +0100 [thread overview]
Message-ID: <20141103083336.7b4da4c2@free-electrons.com> (raw)
In-Reply-To: <20141102223855.CCFA5B2F3F@busybox.osuosl.org>
Dear Peter Korsgaard,
On Sun, 2 Nov 2014 23:27:01 +0100, Peter Korsgaard wrote:
> diff --git a/package/gdb/Config.in b/package/gdb/Config.in
> index a96df1e..b211878 100644
> --- a/package/gdb/Config.in
> +++ b/package/gdb/Config.in
> @@ -8,7 +8,7 @@ config BR2_PACKAGE_GDB
> # target, we don't allow building a separate gdbserver. The
> # one from the external toolchain should be used.
> select BR2_PACKAGE_GDB_SERVER if \
> - (!BR2_PACKAGE_GDB_DEBUGGER && !BR2_TOOLCHAIN_EXTERNAL_GDB_SERVER_COPY)
> + (!BR2_PACKAGE_GDB_DEBUGGER && !BR2_TOOLCHAIN_EXTERNAL_GDB_SERVER_COPY)
Is this really the rule that we want for Config.in file? I do prefer to
align with the previous line rather than enforcing the use of a fixed
number of tabs. But I guess it's a matter of taste.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-03 7:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 22:27 [Buildroot] [git commit] package: indentation cleanup Peter Korsgaard
2014-11-03 7:33 ` Thomas Petazzoni [this message]
2014-11-03 8:00 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2015-06-22 21:05 Peter Korsgaard
2015-06-18 21:41 Thomas Petazzoni
2015-01-15 8:41 Thomas Petazzoni
2014-12-30 10:17 Peter Korsgaard
2014-12-24 10:41 Thomas Petazzoni
2014-12-22 8:27 Thomas Petazzoni
2014-12-20 20:48 Thomas Petazzoni
2014-12-10 20:53 Thomas Petazzoni
2014-10-26 4:47 Peter Korsgaard
2014-10-25 8:38 Thomas Petazzoni
2014-10-24 23:11 Peter Korsgaard
2014-10-23 20:13 Thomas Petazzoni
2014-10-02 20:43 Peter Korsgaard
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=20141103083336.7b4da4c2@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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