X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f Date: Tue, 18 Mar 2014 12:57:29 -0400 Message-Id: <201403181657.s2IGvTv0011043@envy.delorie.com> From: DJ Delorie To: geda-user AT delorie DOT com In-reply-to: (message from Hannu Vuolasaho on Tue, 18 Mar 2014 10:23:13 +0300) Subject: Re: [geda-user] pcb-20140316 is released References: <201403170355 DOT s2H3tavv007601 AT envy DOT delorie DOT com> <532741F8 DOT 8090101 AT buffalo DOT edu> <201403171845 DOT s2HIj1kj012076 AT envy DOT delorie DOT com> <20140317185419 DOT GB5081 AT localhost DOT localdomain> <201403171856 DOT s2HIuDTJ012716 AT envy DOT delorie DOT com>,<53274686 DOT 7000403 AT buffalo DOT edu> Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > However I would like to see some git magic to happen and > when I click window about I would get date of the last commit > and commit ID. I sometimes forget to pull before make. > The compilation date is also nice feature. The tricky part is deciding if a "git pull" causes a rebuild on its own. If you tweak the docs, do you get a new executable? Also, what happens if you're building a tarball that doesn't have git info? We used to put cvs revisions in our files, but we've stripped them all out as a "bad idea" (despite the git conversion). Note that the About window *does* have the release version (20140316 for example) for released versions. Alternately, we could commit a "datestamp" every night, so that there's always a new source file to build...