From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Simon Marchi <simark@simark.ca>,
Joel Brobecker <brobecker@adacore.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] Add git sha information to the gdb version string
Date: Fri, 27 Mar 2020 16:18:47 +0000 [thread overview]
Message-ID: <20200327161847.GD587@embecosm.com> (raw)
In-Reply-To: <87blohby8f.fsf@igel.home>
* Andreas Schwab <schwab@linux-m68k.org> [2020-03-27 16:42:40 +0100]:
> On Mär 27 2020, Andrew Burgess wrote:
>
> > diff --git a/gdbsupport/remote-repository b/gdbsupport/remote-repository
> > new file mode 100644
> > index 00000000000..c05f3163e81
> > --- /dev/null
> > +++ b/gdbsupport/remote-repository
> > @@ -0,0 +1,2 @@
> > +pattern:sourceware.org/git/binutils-gdb.git
> > +branch:master
>
> That doesn't match.
>
> $ git remote -v
> origin git://sourceware.org/git/binutils-gdb (fetch)
> origin ssh://sourceware.org/git/binutils-gdb (push)
OK, thanks for highlighting this. I'll drop the '.git' extension.
Thanks,
Andrew
>
> Andreas.
>
> --
> Andreas Schwab, schwab@linux-m68k.org
> GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
> "And now for something completely different."
next prev parent reply other threads:[~2020-03-27 16:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 11:48 [RFC] " Andrew Burgess
2020-03-26 14:55 ` Simon Marchi
2020-03-27 11:45 ` Andrew Burgess
2020-03-27 12:27 ` [PATCH 0/2] Adding git sha information to the " Andrew Burgess
2020-03-27 12:27 ` [PATCH 1/2] gdbsupport: Resolve shellcheck issues in create-version.sh script Andrew Burgess
2020-03-27 13:11 ` Simon Marchi
2020-03-27 13:57 ` Andrew Burgess
2020-03-27 12:27 ` [PATCH 2/2] Add git sha information to the gdb version string Andrew Burgess
2020-03-27 13:56 ` Simon Marchi
2020-03-27 15:28 ` Andrew Burgess
2020-03-27 15:42 ` Andreas Schwab
2020-03-27 16:18 ` Andrew Burgess [this message]
2020-03-27 15:48 ` Simon Marchi
2020-04-10 0:01 ` Joel Brobecker
2020-04-10 0:10 ` Joel Brobecker
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=20200327161847.GD587@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=schwab@linux-m68k.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).