History log of /dragonfly/games/battlestar/command2.c (Results 1 – 4 of 4)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2
# 4318c66e 27-Jun-2020 Sascha Wildner <saw@online.de>

Sync various games with NetBSD, in order to fix building with -fno-common.

Namely, adventure(6), backgammon(6), battlestar(6), hack(6) and trek(6).

-fno-common will be default in future compilers (

Sync various games with NetBSD, in order to fix building with -fno-common.

Namely, adventure(6), backgammon(6), battlestar(6), hack(6) and trek(6).

-fno-common will be default in future compilers (GCC 10, for example).

show more ...


Revision tags: v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc
# 13fca3df 28-Jan-2018 zrj <rimvydas.jasinskas@gmail.com>

games: Add FALLTHROUGH where missing.


Revision tags: v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1, v4.8.0, v4.6.2, v4.9.0, v4.8.0rc, v4.6.1, v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3, v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc, v4.2.4, v4.3.1, v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc, v4.0.5, v4.0.4, v4.0.3, v4.0.2, v4.0.1, v4.0.0, v4.0.0rc3, v4.0.0rc2, v4.0.0rc, v4.1.0, v3.8.2, v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc, v3.6.2, v3.6.1, v3.6.0, v3.7.1, v3.6.0rc, v3.7.0, v3.4.3, v3.4.2, v3.4.0, v3.4.1, v3.4.0rc, v3.5.0, v3.2.2, v3.2.1, v3.2.0, v3.3.0, v3.0.3, v3.0.2, v3.0.1, v3.1.0, v3.0.0
# 86d7f5d3 26-Nov-2011 John Marino <draco@marino.st>

Initial import of binutils 2.22 on the new vendor branch

Future versions of binutils will also reside on this branch rather
than continuing to create new binutils branches for each new version.


Revision tags: v2.12.0, v2.13.0
# 937f07e0 23-May-2011 Sascha Wildner <saw@online.de>

mail(1) & battlestar(6): Rename some files.

All these files had names which are reserved in Windows, which led
to our tree being not correctly checked out to NTFS, for example.

Reported-by: Adam Ho

mail(1) & battlestar(6): Rename some files.

All these files had names which are reserved in Windows, which led
to our tree being not correctly checked out to NTFS, for example.

Reported-by: Adam Hoka <adam.hoka@gmail.com>

show more ...