public inbox for frysk-cvs@sourceware.org help / color / mirror / Atom feed
From: cagney@sourceware.org To: frysk-cvs@sourceware.org Subject: [SCM] master: Bump mainline version number; and mention test build in release process. Date: Thu, 03 Apr 2008 20:10:00 -0000 [thread overview] Message-ID: <20080403201039.23326.qmail@sourceware.org> (raw) The branch, master has been updated via 027aad2c28f71e9bdd25b3069ea2f392418bcd14 (commit) from a497770c3337305f8caa150835fe1284e9069b83 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email. - Log ----------------------------------------------------------------- commit 027aad2c28f71e9bdd25b3069ea2f392418bcd14 Author: Andrew Cagney <cagney@redhat.com> Date: Thu Apr 3 16:10:02 2008 -0400 Bump mainline version number; and mention test build in release process. ----------------------------------------------------------------------- Summary of changes: frysk-common/ChangeLog | 4 +++ frysk-common/version.in | 2 +- htdocs/releases/index.html | 53 ++++++++++++++++++++++++++++++++----------- 3 files changed, 44 insertions(+), 15 deletions(-) First 500 lines of diff: diff --git a/frysk-common/ChangeLog b/frysk-common/ChangeLog index b2ede63..4444b75 100644 --- a/frysk-common/ChangeLog +++ b/frysk-common/ChangeLog @@ -1,3 +1,7 @@ +2008-04-03 Andrew Cagney <cagney@redhat.com> + + * version.in: Bump to 0.2.50. + 2008-04-02 Andrew Cagney <cagney@redhat.com> * manpages.sh: Recognize ENTITY volumes. diff --git a/frysk-common/version.in b/frysk-common/version.in index eed9179..860e057 100644 --- a/frysk-common/version.in +++ b/frysk-common/version.in @@ -1 +1 @@ -0.0.1.2007.10.24 +0.2.50 diff --git a/htdocs/releases/index.html b/htdocs/releases/index.html index df72627..689b6d1 100755 --- a/htdocs/releases/index.html +++ b/htdocs/releases/index.html @@ -149,23 +149,40 @@ was set above: <ul> -<li>First lets create a tar ball from the head of the branch. It's a -little convoluted since it find's the branch head's shar1 and then -uses that. - +<li>First lets find the shar1 of the branch head (so that it can be +refered to later), and the corresponding release tag: <pre> -echo version=$version branch=$branch +echo branch=$branch shar1=`git-rev-list -n1 $branch` echo shar1=$shar1 -rm -rf frysk-$version -git archive --prefix=frysk-$version/ $shar1 | tar xpf - -tar cfj frysk-$version.tar.bz2 frysk-$version +release=`git show $shar1:frysk-common/version.in` +echo release=$release +</pre> + +<li>Then create a tar-ball using that shar1 marker: +<pre> +rm -rf frysk-$release +git archive --prefix=frysk-$release/ $shar1 | tar xpf - +tar cfj frysk-$release.tar.bz2 frysk-$release </pre> </li> -<li>Assuming you're happy with that, tag the release: +<li>as a sanity check try to build the tar-ball locally: <pre> -git tag -u <gpg-name> -m frysk-$version $shar1 +rm -rf build-$release && mkdir build-$release +( cd build-$release \ + && bunzip2 < ../frysk-$release.tar.bz2 | tar xpf - \ + && mkdir build \ + && cd build \ + && ../frysk-$release/autogen.sh \ + && make -j2 ) +</pre> +</li> + +<li>finally, assuming the results are good, tag the release and push +it: +<pre> +git tag -u <gpg-name> -m frysk-$release $shar1 git push --tags </pre> </li> @@ -177,10 +194,18 @@ git push --tags <p>You might need access to sourceware for this: <pre> -chmod a=r frysk-$version.tar.bz2 -scp frysk-$version.tar.bz2 'sourceware.org:~ftp/pub/frysk' -printf "\n\t\t\tFrysk $version\n\n\t`md5sum frysk-$version.tar.bz2`\n\t$shar1 GIT\n\n" \ - | ssh sourceware.org 'rm -f ~ftp/pub/frysk/.message && dd of=~ftp/pub/frysk/.message && chmod a=r ~ftp/pub/frysk/.message' +chmod a=r frysk-$release.tar.bz2 +scp frysk-$release.tar.bz2 'sourceware.org:~ftp/pub/frysk' +ssh sourceware.org 'rm -f ~ftp/pub/frysk/.message' +cat <<EOF | ssh sourceware.org 'dd of=~ftp/pub/frysk/.message' + + Frysk $release + + `md5sum frysk-$release.tar.bz2` + $shar1 GIT SHAR1 + +EOF +ssh sourceware.org 'chmod a=r ~ftp/pub/frysk/.message' </pre> <!-- end text --> hooks/post-receive -- frysk system monitor/debugger
reply other threads:[~2008-04-03 20:10 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=20080403201039.23326.qmail@sourceware.org \ --to=cagney@sourceware.org \ --cc=frysk-cvs@sourceware.org \ --cc=frysk@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).