From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simark@simark.ca>,
Joel Brobecker <brobecker@adacore.com>,
Andrew Burgess <andrew.burgess@embecosm.com>
Subject: [PATCH 0/2] Adding git sha information to the version string
Date: Fri, 27 Mar 2020 12:27:10 +0000 [thread overview]
Message-ID: <cover.1585311874.git.andrew.burgess@embecosm.com> (raw)
In-Reply-To: <47128465-bbae-6241-6b04-929163f15229@simark.ca>
Following up to Simon's feedback:
1. Patch #1 now make create-version.sh shellcheck clean.
2. Patch #2 keeps create-version.sh shellcheck clean, and adds more
comments throughout.
Thanks
Andrew
---
Andrew Burgess (2):
gdbsupport: Resolve shellcheck issues in create-version.sh script
Add git sha information to the gdb version string
gdb/ChangeLog | 5 ++
gdb/Makefile.in | 2 +-
gdbserver/ChangeLog | 5 ++
gdbserver/Makefile.in | 2 +-
gdbsupport/ChangeLog | 9 ++++
gdbsupport/create-version.sh | 108 +++++++++++++++++++++++++++++++++++++++----
gdbsupport/remote-repository | 2 +
7 files changed, 123 insertions(+), 10 deletions(-)
create mode 100644 gdbsupport/remote-repository
--
2.14.5
next prev parent reply other threads:[~2020-03-27 12:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 11:48 [RFC] Add git sha information to the gdb " Andrew Burgess
2020-03-26 14:55 ` Simon Marchi
2020-03-27 11:45 ` Andrew Burgess
2020-03-27 12:27 ` Andrew Burgess [this message]
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
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=cover.1585311874.git.andrew.burgess@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@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