Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>, Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Sort #includes in gdb
Date: Wed, 03 Apr 2019 19:00:00 -0000	[thread overview]
Message-ID: <898eb4d9-9c21-9dee-0291-ce82251e6c42@redhat.com> (raw)
In-Reply-To: <d077cc5fe3eb77bdb85ffa2ec2ca306c@polymtl.ca>

On 03/29/2019 09:05 PM, Simon Marchi wrote:
> 
> I don't think I've mentioned it, but I really like this change.  I don't like the mental weight of having to choose where to add my include in an unorganized list :).

Me too.  I'm waiting for this to land before touching the "namespace gdb"
work again, since a not-insignificant part of that work revolves around
moving "#include"s in the middle of files to the top of the file.

Thanks,
Pedro Alves


  parent reply	other threads:[~2019-04-03 19:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-26 15:40 Tom Tromey
2019-01-27  4:58 ` Joel Brobecker
2019-02-15 20:46   ` Tom Tromey
2019-01-28 19:08 ` Pedro Alves
2019-01-28 22:31   ` Matt Rice
2019-02-15 20:55   ` Tom Tromey
2019-03-15 23:13     ` Tom Tromey
2019-03-20 17:42       ` Pedro Alves
2019-03-29 20:52         ` Tom Tromey
2019-03-29 21:05           ` Simon Marchi
2019-03-30 18:35             ` Tom Tromey
2019-04-03 18:58               ` Pedro Alves
2019-04-03 19:29                 ` Sergio Durigan Junior
2019-04-03 20:34                 ` Sergio Durigan Junior
2019-04-04  2:47                   ` Tom Tromey
2019-04-04  3:40                     ` Sergio Durigan Junior
2019-04-03 19:00             ` Pedro Alves [this message]
2019-04-03 20:11               ` Tom Tromey
2019-04-03 21:00                 ` Pedro Alves

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=898eb4d9-9c21-9dee-0291-ce82251e6c42@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    --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