Seems that these options were dropped between flac 1.0.3 (of July 2002) and flac 1.0.4 (of September 2002).Never noticed. I was actually referring to the website and source code documentation, but removing this is probably also a good idea. I understand that the commit Whats wrong with using the commit date to compare?I already explain that: a commit number doesn't show the code base version it refers to. How will I know the code base version of commit 3022dad8 in ten years time ? hash is hard to keep track of, but what about the commit date. I don't understand why it's a blocker for you. "1.3.4git-blabla" clearly shows it's not a release but a test version.I'll quote myself: Current git would be marked 1.3.4 but is probably closer to 1.4.0 or something. The version number 1.3.4 belongs to a specific release. As soon as something is added or removed, it is no longer that release, and it is in my view no longer version 1.3.4. Having version number 1.3.4git-hash suggest it is 1.3.4, but it isn't. We don't care about what ffmpeg is doing, seriously.You are the one who came up with ffmpeg in the first place. Maybe listen to your users ?I've listened, and I didn't find the arguments compelling. I'm doing this in my own time, unpaid, because I like FLAC. It is taking up pretty much all of my free time, fixing bugs and security issues that most users will never notice. Maybe you rather have me stop doing any work on FLAC at all?