From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Sort #includes in gdb
Date: Wed, 20 Mar 2019 17:42:00 -0000 [thread overview]
Message-ID: <f172a298-809a-d928-9f5f-f65300826be2@redhat.com> (raw)
In-Reply-To: <87r2b7viht.fsf@tromey.com>
On 03/15/2019 11:13 PM, Tom Tromey wrote:
> Pedro> ISTR that you could point the bot at some branch instead of a patch?
>
> Tom> I don't know but I will ask Sergio when he's back.
>
> I think it can't be done.
Isn't that what "try --branch" is for?
>
> Pedro> No firm opinion on comments vs no comments.
>
> Tom> For now at least, I'm sticking with "no comments" because the lack of
> Tom> comment-handling in the script means that adding comments makes the
> Tom> script non-idempotent. But, idempotency is a good quality to have,
> Tom> because it means the script can be re-run at any time to fix any
> Tom> "regressions" that have crept in.
>
> I thought about this some more and I went back and implemented limited
> comment-scanning, to make this work. I think this is nicer because it
> provides an in-source guide to developers saying where to add a new
> #include.
>
> I've appended the relevant bits from the rewritten objfiles.c.
>
> Let me know what you think.
Seems fine to me.
BTW, I noticed that the ChangeLog said "Sort headers."
twice for every entry.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2019-03-20 17:42 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 [this message]
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
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=f172a298-809a-d928-9f5f-f65300826be2@redhat.com \
--to=palves@redhat.com \
--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