From: Christian Biesinger <cbiesinger@google.com>
To: Jonny Grant <jg@jguk.org>
Cc: gdb@sourceware.org
Subject: Re: [PATCH] change bug url to https in gdb --help
Date: Tue, 9 Jun 2020 13:24:22 -0500 [thread overview]
Message-ID: <CAPTJ0XH6GYB+yjFbwsJ1a4h8RA1TKQ7MpSu_gdpoCbFEm3rkFg@mail.gmail.com> (raw)
In-Reply-To: <db2887a9-f36a-7429-184a-77e02b851302@jguk.org>
On Tue, Jun 9, 2020 at 7:20 AM Jonny Grant <jg@jguk.org> wrote:
> 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
>
> Hi Christian
>
> Thank you for the links.
>
> There's a small typo on that ContributionChecklist wiki. Signed up, but can't edit the page.
>
> "of they will be rejected during mailing list moderation"
> ^ should be "or"
Thanks, I fixed the typo, although I am not sure that sentence is
right -- I don't think gdb-patches is moderated?
Christian
next prev parent reply other threads:[~2020-06-09 18:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 22:20 Jonny Grant
2020-05-28 19:05 ` Christian Biesinger
[not found] ` <42e8834a-5903-0423-9309-5ac57c710578@jguk.org>
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 [this message]
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=CAPTJ0XH6GYB+yjFbwsJ1a4h8RA1TKQ7MpSu_gdpoCbFEm3rkFg@mail.gmail.com \
--to=cbiesinger@google.com \
--cc=gdb@sourceware.org \
--cc=jg@jguk.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