Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: Gary Benson <gbenson@redhat.com>,  gdb-patches@sourceware.org
Subject: Re: [PATCH] Remove duplicate or commented-out #includes
Date: Wed, 23 Jan 2019 04:00:00 -0000	[thread overview]
Message-ID: <87sgxknhve.fsf@tromey.com> (raw)
In-Reply-To: <87muntpc6z.fsf@tromey.com> (Tom Tromey's message of "Mon, 21 Jan	2019 21:07:32 -0700")

>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:

Tom> I wrote a script to sort the includes.  The output is rather voluminous,
Tom> not totally sure yet how I will submit it.

If anyone wants to look, it is on the branch submit/sort-includes in my
github.  The patch is pretty big... maybe I can gzip it.  Or maybe I can
submit it in pieces, since really each .c change is independent.

There's also a submit/common-includes branch, which normalizes gdb to
use #include "common/name.h", and removes the -Icommon from the
Makefiles.  I'll clean this one up and submit it soon.

Tom


  reply	other threads:[~2019-01-23  4:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-19 21:31 Tom Tromey
2019-01-21 17:34 ` Simon Marchi
2019-01-21 18:28   ` Tom Tromey
     [not found] ` <20190121172843.GA7007@blade.nx>
2019-01-22  4:07   ` Tom Tromey
2019-01-23  4:00     ` Tom Tromey [this message]
2019-01-23 16:40     ` 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=87sgxknhve.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gbenson@redhat.com \
    --cc=gdb-patches@sourceware.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