shellfu

Struktur: f872308193

Autor	SHA1	Nachricht	Datum
Alois Mahdal	f40b74432d	Update MKit to v0.0.39	vor 4 Jahren
Alois Mahdal	ef4887123b	Update MKit to v0.0.36	vor 5 Jahren
Alois Mahdal	d5d327e157	Update MKit to v0.0.28	vor 6 Jahren
Alois Mahdal	b60574a399	Update MKit to v0.0.26	vor 6 Jahren
Alois Mahdal	25ceea5816	Update MKit to v0.0.24	vor 6 Jahren
Alois Mahdal	5a8e516e37	Update MKit to v0.0.21	vor 7 Jahren
Alois Mahdal	9e67f5f3c5	Update MKit to v0.0.17	vor 7 Jahren
Alois Mahdal	80dc119bde	Update MKit to v0.0.15	vor 7 Jahren
Alois Mahdal	22c8a83421	Update MKit to v0.0.14	vor 8 Jahren
Alois Mahdal	9f6638aa81	Update MKit to v0.0.13	vor 8 Jahren
Alois Mahdal	1751362614	Update MKit to v0.0.10	vor 8 Jahren
Alois Mahdal	747947ddde	Update MKit to version 0.0.8	vor 8 Jahren
Alois Mahdal	e878eb6bd8	Update Mkit to v0.0.1	vor 9 Jahren
Alois Mahdal	b68913c9cb	Apply changes suggested by ShellCheck (mkit)	vor 9 Jahren
Alois Mahdal	36adafec09	Add check on version bump In mkit's world, last change before release (ie. the commit that gets tagged) must be nothing but version bump in "config.mk"	vor 9 Jahren
Alois Mahdal	9a335940c4	Die sooner if last tag cannot be found Other checks that rely on version number that is derived from this tag would then give weird messages.	vor 9 Jahren
Alois Mahdal	39a973338b	Move mkit to a subdirectory	vor 9 Jahren
Alois Mahdal	4fba933b7f	Remove STAGE (later known as PRERELEASE) from tag comment Folow-up to 37b5db9 and 9c94a46.	vor 9 Jahren
Alois Mahdal	9f9b925005	Use nicer layout for release checks	vor 9 Jahren
Alois Mahdal	9c94a46bcc	Remove pre-release info Turns out that get_version and release.sh strategy do not agree very well on this, which may end up as version comparison problem. SemVer 2.0 says that pre-release versions go before the associated versions, that is, 1.0.0-blah goes before 1.0.0, and at the same time remove the compatibility guarantee. This means that if pre-releases are needed, we will probably need to change both PRERELEASE and VERSION, which is not what was expected when writing release.sh. For now, the safe thing is to remove PRERELEASE altogether. If we ever need to do a pre-release, we will re-verify if it works properly; until then, build meta-data give us enough luxury.	vor 9 Jahren
Alois Mahdal	914395eee0	Add release_? action for controlled release routine	vor 9 Jahren

17 Commits (f872308193460185c0dcbc14288f0b473fac0c29)