public inbox for src-cvs@sourceware.org help / color / mirror / Atom feed
From: willnewton@sourceware.org To: src-cvs@sourceware.org Subject: gdb and binutils branch master updated. 2536ee9d03cb7c4af97bf4b29429bef3c30652c2 Date: Wed, 27 Aug 2014 12:51:00 -0000 [thread overview] Message-ID: <20140827125122.19369.qmail@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gdb and binutils". The branch, master has been updated via 2536ee9d03cb7c4af97bf4b29429bef3c30652c2 (commit) from 7322eefb9ee1c3b00a2ec3649778b733e43c7b35 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=2536ee9d03cb7c4af97bf4b29429bef3c30652c2 commit 2536ee9d03cb7c4af97bf4b29429bef3c30652c2 Author: Will Newton <will.newton@linaro.org> Date: Thu Aug 7 14:38:55 2014 +0100 src-release.sh: Convert src-release to a shell script This began as an attempt to make a few small changes to src-release but heeding the comments at the top of the file it seemed it might be wise to convert it to a shell script instead which should hopefully be more maintainable. This shell script contains most of the functionality of the Makefile version. It can be run like this: # This will build gdb and compress with bzip2, gzip and xz ./src-release.sh -bgx gdb The functionality that has been removed is building tarballs for insight and gnats, which were broken in the current repository layout and gas+binutils which amounted to basically the same thing as binutils so didn't seem worth keeping. The script always builds a tar file, compression is optional, so no need for specific commands to build tar files rather than compressed tar files. The build of gas releases has been fixed, as has extraction of version numbers which had been broken since the switch to configure.ac files and AC_INIT. I also removed the code for distcleaning the intl sub-directory as it seems like that issue has been fixed. The script is capable of compressing with bzip2, gzip and xz which should cover all formats available on gnu.org. I tested it by producing release tarballs which are substantially identical to the ones produced by the src-release script. ChangeLog: 2014-08-27 Will Newton <will.newton@linaro.org> * src-release.sh: New file. * src-release: Remove file. ----------------------------------------------------------------------- Summary of changes: ChangeLog | 5 + src-release | 318 -------------------------------------------------- src-release.sh | 352 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 357 insertions(+), 318 deletions(-) delete mode 100644 src-release create mode 100755 src-release.sh hooks/post-receive -- gdb and binutils
reply other threads:[~2014-08-27 12:51 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=20140827125122.19369.qmail@sourceware.org \ --to=willnewton@sourceware.org \ --cc=src-cvs@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: linkBe 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).