From: Jonny Grant <jg@jguk.org>
To: Christian Biesinger <cbiesinger@google.com>
Cc: gdb@sourceware.org
Subject: Re: [PATCH] change bug url to https in gdb --help
Date: Sat, 30 May 2020 00:45:39 +0100 [thread overview]
Message-ID: <42e8834a-5903-0423-9309-5ac57c710578@jguk.org> (raw)
In-Reply-To: <CAPTJ0XE=+pcqywEQD++rrkbCx-62w-QnLU8=eyOWTh7gZbnhEQ@mail.gmail.com>
Many thanks Christian
Will send to gdb-patches now with the ChangeLog.
Unfortunately my Ubuntu LTS git is stuck on 2.17.1 without the git-send-email command for the moment. I'll paste in an
email to allow better comments.
Regards, Jonny
On 28/05/2020 20:05, Christian Biesinger wrote:
> Thanks for the patch! This looks good to me, though I can't officially
> approve patches. But could you send patches to
> gdb-patches@sourceware.org?
>
> Also, it would be great if you could set up git-send-email for sending
> patches, as that makes it easier to comment on them (it sends them
> inline in the email)
>
> Finally, patches require a changelog entry, please add one:
> https://sourceware.org/gdb/wiki/ContributionChecklist#ChangeLog
> https://sourceware.org/gdb/wiki/ContributionChecklist#Properly_Formatted_GNU_ChangeLog
>
> Thanks again,
> Christian
>
> On Wed, May 27, 2020 at 5:20 PM Jonny Grant <jg@jguk.org> wrote:
>>
>> Please find attached
>> Jonny
next prev parent reply other threads:[~2020-05-29 23:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 22:20 Jonny Grant
2020-05-28 19:05 ` Christian Biesinger
2020-05-29 23:45 ` Jonny Grant [this message]
2020-05-30 15:26 ` Simon Marchi
2020-05-30 15:36 ` Jonny Grant
2020-06-10 13:12 ` Jonny Grant
2020-06-09 12:20 ` Jonny Grant
2020-06-09 18:24 ` Christian Biesinger
2020-06-11 2:27 ` Simon Marchi
2020-06-11 15:57 ` Pedro Alves
2020-06-11 19:29 ` Christian Biesinger
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=42e8834a-5903-0423-9309-5ac57c710578@jguk.org \
--to=jg@jguk.org \
--cc=cbiesinger@google.com \
--cc=gdb@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).