On Fri, 8 Apr 2022 18:34:14 +0200 Ichthyostega <p...@ichthyostega.de> wrote:
>> On Fri, 8 Apr 2022 17:42:30 +0200 Ichthyostega <p...@ichthyostega.de> wrote: >>> You can let Git do the hard work ;-) >>> >>> git rev-parse --short=4 <commithash> > >Am 08.04.22 um 18:20 schrieb Will Godfrey: >> That's interesting. So if I understand that right it's always going to be >> exactly one commit behind - you can't set it *as* the new hash is being built >> as that would in itself change it! > > >Ha! Good point. > >What I have noticed is that when projects switch to using the Git hash, >they typically also stop recording the build-number in the commit. >Rather, the Git commit will be read by the build system and just >incorporated into a generated "definitions" header, which is then >used to embed constant strings into the source code or UI definitions. > >-- Hermann That all sounds rather convoluted, and I don't see how it provides anything that ordinary users could see and report. >PS: many modern projects also stop using hand written release note files. >The developers from the "java script generation" typically strongly resent >against such old fashioned habits, since "the computer can do that for us". It was one of the debian packagers who asked me to change for Cal's 'notes' to 'Changelog' >Well, hereby I confess to be old-fashioned. I do value a hand written >release notes file, because I prefer a human having spent some brain cycles >into figuring out what was really relevant and what was just noise. :) -- Will J Godfrey https://willgodfrey.bandcamp.com/ http://yoshimi.github.io Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song. _______________________________________________ Yoshimi-devel mailing list Yoshimi-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/yoshimi-devel
