public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: <Paul.Koning@dell.com>
Cc: <sergiodj@redhat.com>,  <gdb-patches@sourceware.org>
Subject: Re: [PATCH] fix build failure with Python 3.7
Date: Fri, 01 Jun 2018 01:27:00 -0000	[thread overview]
Message-ID: <87efhrpa8g.fsf@tromey.com> (raw)
In-Reply-To: <2BFDF702-C2E4-4339-ABB4-D0655063DE95@dell.com> (Paul Koning's	message of "Thu, 31 May 2018 20:45:40 +0000")

>>>>>   <Paul.Koning@dell.com> writes:

>> This bug number is actually from Python's bugzilla, not GDB's.  So it's
>> not correct to mention it here in the ChangeLog/commit message.  AFAIK,
>> there's no correspondent GDB bug filed for this issue.

> Ok, I removed that.

There may be other cases where we stick a URL of some non-gdb bug into
the ChangeLog (or at least the commit message), and that seems like it
would save some time for some future archaeologist, so I'd suggest doing
that.

Tom

  reply	other threads:[~2018-06-01  1:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31 18:20 Paul.Koning
2018-05-31 20:45 ` Sergio Durigan Junior
2018-05-31 21:25   ` Paul.Koning
2018-06-01  1:27     ` Tom Tromey [this message]
2018-06-01 11:58       ` Phil Muldoon
     [not found]     ` <87d0xb34jw.fsf@redhat.com>
2018-06-01 11:56       ` Phil Muldoon
2018-06-01 12:16     ` Pedro Alves
2018-06-01 12:54       ` Paul.Koning
2018-06-01 13:10         ` Pedro Alves
2018-06-01 13:22           ` Paul.Koning
2018-06-01 13:36             ` Pedro Alves
2018-06-01 13:37               ` Pedro Alves
2018-06-01 13:47                 ` Paul.Koning
2018-06-08 14:35                   ` Pedro Alves
2018-06-08 14:37                     ` Paul.Koning
2018-06-08 14:55                       ` Pedro Alves
2018-06-08 17:36                         ` Paul.Koning
2018-06-09  0:26                           ` Sergio Durigan Junior

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=87efhrpa8g.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=Paul.Koning@dell.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).