You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whether rebasing to, merging-rebasing to, or merging an upstream tag, or
not integrating an upstream tag at all, we must figure out the best base
tag. So far, I tried several strategies:
- `--first-parent`: This works only for merging-rebases
- `--exclude='*.windows.*'`: This works if integrating an upstream tag,
but not when a `.windows.2` version is desired
- calling `git describe` twice: first to figure out the reachable
upstream tag that is closest to the revision, and then
calling it a second time, this time allowing for a Git for Windows
tag. If the two searches came up with different results, pick the
most recent one.
Unfortunately that did not work. Its logic relies on the date when the
Git version the downstream Git for Windows version was tagged.
This broke down in the case of v2.50.1, which was tagged before I
could release v2.50.0.windows.1.
Let's just instead pick the higher version number by leveraging the
`version_compare` function I developed in
git-for-windows/build-extra@1418ee7e8e
(git-update: do not suggest downgrading from an -rc version, 2017-10-26)
and that has been subsequently been enhanced in that repository.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
0 commit comments