From: Jonny Grant <jg@jguk.org>
To: Simon Marchi <simark@simark.ca>,
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 16:36:20 +0100 [thread overview]
Message-ID: <9ff0194c-f378-fd83-d1cd-2974d334c994@jguk.org> (raw)
In-Reply-To: <bf5abc23-18e7-41c3-cda8-59e0628cb439@simark.ca>
On 30/05/2020 16:26, Simon Marchi wrote:
> On 2020-05-29 7:45 p.m., Jonny Grant wrote:
>> 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.
>
> It's been available for ages, it's not a matter of old git. It's just that it's
> packaged separately:
>
> https://packages.ubuntu.com/bionic/git-email
>
> The packages.ubuntu.com interface (derived from packages.debian.org) is handy to
> find which package provides a given file. For example to find that the git-email
> package provides the git-send-email file:
>
> https://packages.ubuntu.com/search?suite=bionic&arch=amd64&mode=exactfilename&searchon=contents&keywords=git-send-email
>
> Alternatively, the `apt-file` package gives you the same functionality locally.
>
> Simon
>
Many thanks. I've installed the package and will use git send-email next time
Jonny
next prev parent reply other threads:[~2020-05-30 15:36 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
2020-05-30 15:26 ` Simon Marchi
2020-05-30 15:36 ` Jonny Grant [this message]
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=9ff0194c-f378-fd83-d1cd-2974d334c994@jguk.org \
--to=jg@jguk.org \
--cc=cbiesinger@google.com \
--cc=gdb@sourceware.org \
--cc=simark@simark.ca \
/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).