Closed adrelanos closed 8 years ago
Why not git verify-commit <commit>
?
Master is supposed to stay usable and permanent, with experimental stuff going into other branches, e.g. I just uploaded https://github.com/rustybird/corridor/tree/qubes/qubes
Whonix corridor instructions WIP: https://www.whonix.org/wiki/Corridor
Nice, thanks! By the way, I'm working on automatically setting up a logging DNS server, similar to how it's done in orplug.
Master is supposed to stay usable and permanent, with experimental stuff going into other branches, e.g. I just uploaded https://github.com/rustybird/corridor/tree/qubes/qubes
Cool!
Which version number would we give the package if it gets uploaded to the Whonix or even Debian repository?
Perhaps we just count the number of git commits and use that as version number?
I think the ISO 8601 timestamp (without separators) of the last commit is often used, e.g. corridor-20160704102229
Do you know the git command to create this format?
Maybe something like
git show --no-patch --pretty=format:%ai <commit> |
tr -dc 0-9 |
cut -b 1-14
I find these version numbers difficult to read, but it's your call.
Whonix corridor instructions WIP: https://www.whonix.org/wiki/Corridor
It would help if there was a release, a signed git tag that users could be pointed at.