[Parted-commits] GNU Parted Official Repository: Changes to 'master'

[Joel Granados]

 README-release           |    5 ++---
 build-aux/parted-release |    2 +-
 2 files changed, 3 insertions(+), 4 deletions(-)

New commits:
commit e7977887d5b668fa213c9ab73533fe6df5063436
Author: Joel Granados Moreno <jgranado at redhat.com>
Date:   Thu Jul 23 19:15:19 2009 +0200

    Little fixes before the release.
    
    * README-release: Correct an error in step 5.  In step 6 we mean
    $VERSION.
    * build-aux/parted-release (_do_release): Use '-F -' to make the NEWS
    commit.

diff --git a/README-release b/README-release
index d42febf..1668706 100644
--- a/README-release
+++ b/README-release
@@ -14,11 +14,10 @@ Here is most of the steps we (maintainers) follow when making a release.
 
 5. Wait a few minutes (maybe up to 30?) and then use the release URLs to
    download all tarball/signature pairs and use gpg --verify to ensure that
-   they're all valid.  You will also need to verify these URLs in the
-   announcement mail.
+   they're all valid.  You will also need these URLs in the announcement mail.
 
 6. Push the new tag with the following command:
-     git push origin tag v$v
+     git push origin tag v$VERSION
 
 7. Send the gpg-signed announcement mail, e.g.,
      To: info-gnu at gnu.org, parted-devel at lists.alioth.debian.org
diff --git a/build-aux/parted-release b/build-aux/parted-release
index 9de7122..62157a3 100755
--- a/build-aux/parted-release
+++ b/build-aux/parted-release
@@ -101,7 +101,7 @@ _do_release()
     news_line="* Noteworthy changes in release $v ($date) [stable]"
     commit_message="version $v\n\n* NEWS: Record release date.\n"
     sed -e "s/^.*in release.* (????-??-??) .*/$news_line/" -i NEWS && \
-    git commit NEWS --message="$commit_message" && \
+    printf "$commit_message" | git commit NEWS -F - && \
     git tag $key_string -m "parted $v" v$v HEAD && \
     ./bootstrap && \
     ./configure && \