|author||Mark Wielaard <firstname.lastname@example.org>||2019-06-25 19:22:37 +0200|
|committer||Mark Wielaard <email@example.com>||2019-06-25 19:30:27 +0200|
|parent||Change a magic number (6) for a constant (BZ_N_GROUPS). (diff)|
Add prepare-release.sh script.
Script to run to prepare a new release. It will update the release number and tell you to update the CHANGES file and to double check everything looks before doing the release commit and tagging. Afterwards you probably want to run release-update.sh to upload the release and update the website at https://sourceware.org/bzip2/ There are embedded version strings and dates in a couple of places. To keep the script simple remove some that aren't absolutely necessary. README now just points to CHANGES. README.COMPILATION.PROBLEMS only mentions the version once at the top. bzip2.c only mentions the version once when doing --version. manual.xml now doesn't have any embedded versions, just uses &bz-version; everywhere.
Diffstat (limited to 'bzip2.c')
1 files changed, 1 insertions, 1 deletions
|@@ -1609,7 +1609,7 @@ void license ( void )|
|1609||" \n"||1609||" \n"|
|1610||" This program is free software; you can redistribute it and/or modify\n"||1610||" This program is free software; you can redistribute it and/or modify\n"|
|1611||" it under the terms set out in the LICENSE file, which is included\n"||1611||" it under the terms set out in the LICENSE file, which is included\n"|
|1612||" in the bzip2-1.0.6 source distribution.\n"||1612||" in the bzip2 source distribution.\n"|
|1613||" \n"||1613||" \n"|
|1614||" This program is distributed in the hope that it will be useful,\n"||1614||" This program is distributed in the hope that it will be useful,\n"|
|1615||" but WITHOUT ANY WARRANTY; without even the implied warranty of\n"||1615||" but WITHOUT ANY WARRANTY; without even the implied warranty of\n"|