On Mon, Feb 19, 2018 at 10:55:10PM +0000, we recorded a bogon-computron collision of the <xas...@dbrooke.me.uk> flavor, containing: > On Mon, Feb 19, 2018 at 02:35:51PM -0700, Tom Russo wrote: > > On Mon, Feb 19, 2018 at 08:16:31PM +0000, we recorded a bogon-computron > > collision of the <godfr...@gmail.com> flavor, containing: > > > I could see a slight use case for the date when running with uncommitted > > > code, > > > > Agreed, this has occurred to me, as the git sha1 hash won't reflect that > > you're running modified code. But in this case, the person interested in > > Maybe look at using 'git describe' to provide the entry for the about > box? > > For example, I've used 'git describe --always --dirty=+' which appends a > + if the build is from uncommitted sources.
That is a possibility to beef up the git sha inclusion. It could be done easily, irrespective of whether we pitch the date or not. Just need to change XastirGitStamp.sh. -- Tom Russo KM5VY Tijeras, NM echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] _______________________________________________ Xastir-dev mailing list Xastir-dev@lists.xastir.org http://xastir.org/mailman/listinfo/xastir-dev
