| commit | 2a0b5a0714c2a61a475d636104cae27f739fc18a | |
| author | Johannes Schindelin <johannes.schindelin@gmx.de> | |
| Fri, 20 Mar 2009 12:15:15 +0000 (20 13:15 +0100) | ||
| committer | Johannes Schindelin <johannes.schindelin@gmx.de> | |
| Sun, 22 Mar 2009 19:43:25 +0000 (22 20:43 +0100) | ||
| tree | 2ce694c0ace16d6546bdcd4ae253b168a1f60e7e | treesnapshot (tar.gz zip) |
| parent | 0de1c10f37b18f685a16080e2b41e81dabdca51f | commitdiff |
share/WinGit/release.sh: provide a few safeguards
There are some pitfalls when releasing a new installer: as we want to
be able to recreate every installer, the version from which the
currently installed Git was built needs to be tagged.
Check that (and a few other things), and require the flag "--force" if
any precondition is not met.
The --force flag is needed so that it is still easy to make a quick
"release", e.g. when a bug is fixed (so the bug reporter can verify the
fix).
The order of the checks was chosen by the following measure: the more
interesting the check could be even if the user chose to pass --force
later, the earlier the check is performed.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
There are some pitfalls when releasing a new installer: as we want to
be able to recreate every installer, the version from which the
currently installed Git was built needs to be tagged.
Check that (and a few other things), and require the flag "--force" if
any precondition is not met.
The --force flag is needed so that it is still easy to make a quick
"release", e.g. when a bug is fixed (so the bug reporter can verify the
fix).
The order of the checks was chosen by the following measure: the more
interesting the check could be even if the user chose to pass --force
later, the earlier the check is performed.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
| share/WinGit/release.sh | diffblobblamehistory |