Releases on GitHub are identified by id, not by tag name. So we need a way
to update the list of tag name <-> id correspondences.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
We can just as easily use the same trick as portable/release.sh to
create a second (fake) root directory and add it to the .7z archive by
passing an absolute path (7za.exe will strip the directory from absolute
paths).
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
For backwards-compatibility, we now copy appropriately adjusted versions
of the Git wrapper into /bin/ so that e.g. TortoiseGit/SourceTree find
the same executables as before.
This addresses https://github.com/git-for-windows/git/issues/208
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
install.out sounds too much like a counterpart to install.iss.in, which is
not what install.out is.
Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
The `.rtf` format we used to present our release notes is sadly not as
much of a standard as we hoped, as it is rendered differently depending
whether Word or WordPad, or even which version thereof, is used to
display it.
As we already make extensive use of markdown on GitHub (README, wiki,
comments, etc), it makes sense to maintain the release notes in markdown
format, too.
While at it, add a few changes since 1.9.5 already, even if the next Git
for Windows version needs to wait a few days, still.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Previously, Git for Windows' release notes were provided as an .rtf
file. The intention was to enable somewhat more pleasant formatting than
plain text.
However, the .rtf format is not without flaws: re-saving the same file
in a different editor will change the file on disk even if no textual
content nor formatting was changed. Besides, the formatting of an .rtf
file is sadly not as standardized as we hoped: in Windows 8's WordPad,
the bullet points are displayed differently than in XP's WordPad.
The markdown standard provides all the formatting we would want to have,
and it can be converted easily into HTML which can be displayed just
after Git for Windows was installed. So let's package the Markdown
package for use in any MSys2-based system -- including our Git SDK --
and use it from now on to format our release notes.
To accomodate Git for Windows' Pacman repository structure, we build
architecture dependent versions of the package, even if Markdown is
technically not architecture dependent (by virtue of being a Perl
script).
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
This is a rough port of the inno setup files to the current *MSYS2*
environment. The source files are generated by the `release.sh` into
`file-list.iss`. That file is then included by adding the line
`#include "file-list.iss"` into `install.iss.in`.
The git-cheeta plugin is commented out temporary.
Signed-off-by: nalla <nalla@hamal.uberspace.de>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
This script is so heavily edited that it almost looks like a rewrite,
but it still is essentially the script written by Sebastian Schuberth.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Johannes Schindelin
Paul DelRe
Sebastian Schuberth
nalla