Hi Jim, On Fri, Nov 6, 2009 at 8:17 AM, Jim Meyering <j...@meyering.net> wrote: > Jim Meyering wrote: >> FYI, I've just pushed this to coreutils, so that the following >> from README-release is no longer manual: >> >> * Manually set the date, version number, and [stable/alpha/beta] on >> line 3 of NEWS, then do e.g.,: >> >> v=8.0 >> pkg=$(sed -n 's/^PACKAGE = \(.*\)/\1/p' Makefile) >> git commit -F <(printf 'version '$v'\n\n* NEWS: Record release date.\n') >> -a >> git tag -s -m "$pkg $v" v$v HEAD >> >> The replacement is to do this: >> >> * Set the date, version number, and release type [stable/alpha/beta] on >> line 3 of NEWS, commit that, and tag the release by running e.g., >> >> build-aux/do-release-commit-and-tag 8.1 beta > No one objected, so I've moved it to gnulib as-is.
I noticed that there is a build-aux in coreutils tree, but since there is no do-release-commit-and-tag in there, I think it could be like this: diff --git a/README-release b/README-release index 09b50d7..6d8b824 100644 --- a/README-release +++ b/README-release @@ -32,7 +32,7 @@ FIXME: enable excluded programs like arch? to get their manual pages? * Set the date, version number, and release type [stable/alpha/beta] on line 3 of NEWS, commit that, and tag the release by running e.g., - build-aux/do-release-commit-and-tag 8.1 beta + gnulib/build-aux/do-release-commit-and-tag 8.1 beta * Run the following to create release tarballs. Your choice selects the corresponding upload-to destination in the emitted gnupload command.
