Hi, just so it's clear that nobody external is manipulating our git repos - I'm working on the v2.6.15 release commit, and due to fat fingers / bad timing a "not quite ready" version slipped out to github and gitlab.
I have now force-pushed the "this should be the final commit" to all
repos, so it's consistent, and hopefully the window where the wrong
commit is out there is small enough that not so many people will get
surprised by this.
The current "this is likely to be 2.6.15" commit is
commit 90bdd59a95170169585a171d4993ba0b1851a3f9
Author: Gert Doering <g...@greenie.muc.de>
Date: Sun Sep 21 15:50:10 2025 +0200
preparing release 2.6.15
the one that accidentially escaped was
commit be4d38d142c162537316b271b81cfe4432695c06
Author: Gert Doering <g...@greenie.muc.de>
Date: Sun Sep 21 15:50:10 2025 +0200
preparing release 2.6.15
... which is based on the same parent (t_net.sh fix, so no actual
difference in *code* here), the difference is in last-minute fixes to
"Changes.rst" and "ChangeLog".
No erroneous tags have been pushed.
Apologies for being too impatient and messing this up.
gert
--
"If was one thing all people took for granted, was conviction that if you
feed honest figures into a computer, honest figures come out. Never doubted
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany g...@greenie.muc.de
signature.asc
Description: PGP signature
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
