public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Reuben Thomas via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: A couple of trivial fixes
Date: Mon, 04 Jan 2021 12:33:36 -0700	[thread overview]
Message-ID: <87turwebu7.fsf@tromey.com> (raw)
In-Reply-To: <CAOnWdoiJSmCxtAwz3juuid_1xoyk-+pxiC1=egnRwhFSCxhxng@mail.gmail.com> (Reuben Thomas via Gdb-patches's message of "Sat, 2 Jan 2021 12:16:06 +0000")

>>>>> "Reuben" == Reuben Thomas via Gdb-patches <gdb-patches@sourceware.org> writes:

Reuben> I attach a couple of patches against master as of just now, one to fix the
Reuben> English in a comment, and the other to remove gdb_select.h from
Reuben> gdb/Makefile.in, as it has been moved to gdbsupport/ (this broke "make
Reuben> tags").

Hi.  Thanks for the patches.

Before we can check them in, they both need ChangeLog entries.
See https://sourceware.org/gdb/wiki/ContributionChecklist

Reuben>  binutils/readelf.c | 2 +-

This one should go to the binutils list.

thanks,
Tom

  reply	other threads:[~2021-01-04 19:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-02 12:16 Reuben Thomas
2021-01-04 19:33 ` Tom Tromey [this message]
2021-01-06 21:46   ` Reuben Thomas
2022-03-22 22:10     ` Reuben Thomas
2022-03-23 10:50       ` [PATCHv2 0/3] Fix for 'make tags' build rule Andrew Burgess
2022-03-23 10:50         ` [PATCHv2 1/3] gdb/Makefile.in: remove SOURCES variable Andrew Burgess
2022-03-23 10:50         ` [PATCHv2 2/3] gdb/Makefile.in: fix 'make tags' build target Andrew Burgess
2022-03-23 10:50         ` [PATCHv2 3/3] gdb/Makefile.in: move ALLDEPFILES earlier in Makefile.in Andrew Burgess
2022-04-03 14:50         ` [PATCHv2 0/3] Fix for 'make tags' build rule Andrew Burgess

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=87turwebu7.fsf@tromey.com \
    --to=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).