From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: FYI/pushed: fix gdb version parsing in src-release.sh
Date: Sun, 17 Jan 2016 06:08:00 -0000 [thread overview]
Message-ID: <1453010917-15083-1-git-send-email-brobecker@adacore.com> (raw)
Small change required after we switched the gdb version scheme to
using a -git suffix rather than a -cvs one.
ChangeLog:
* src-release.sh: Compute the gdb tarball name by stripping
'-git' rather than '-cvs'.
Tested by running "src-release.sh gdb" and verifying the tarball
name as well as its contents.
Thanks,
--
Joel
---
src-release.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src-release.sh b/src-release.sh
index 40d0126..64fa4c2 100755
--- a/src-release.sh
+++ b/src-release.sh
@@ -60,7 +60,7 @@ getver()
bfd/configure --version | sed -n -e '1s,.* ,,p'
elif test -f $tool/common/create-version.sh; then
$tool/common/create-version.sh $tool 'dummy-host' 'dummy-target' VER.tmp
- cat VER.tmp | grep 'version\[\]' | sed 's/.*"\([^"]*\)".*/\1/' | sed 's/-cvs$//'
+ cat VER.tmp | grep 'version\[\]' | sed 's/.*"\([^"]*\)".*/\1/' | sed 's/-git$//'
rm -f VER.tmp
elif test -f $tool/version.in; then
head -1 $tool/version.in
--
2.5.0
reply other threads:[~2016-01-17 6:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1453010917-15083-1-git-send-email-brobecker@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@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).