{"thread":{"id":"14038","subject":"Best practice question","startedAt":"2008-06-19T14:32:35Z","lastAt":"2008-06-19T16:39:19Z","messageCount":4,"participants":["D. Stuart Freeman","Karl Hasselström","Santi Béjar","Avery Pennarun"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"80320","messageId":"485A6E03.6090509@et.gatech.edu","threadId":"14038","inReplyTo":null,"subject":"Best practice question","fromName":"D. Stuart Freeman","fromEmail":"stuart.freeman@et.gatech.edu","sentAt":"2008-06-19T14:32:35Z","receivedAt":"2008-06-19T14:32:35Z","isPatch":false,"sender":{"key":"stuart.freeman@et.gatech.edu","avatar":"https://gravatar.com/avatar/d2c9483eaa2fa28008c84e68b765886b118c445b1ddf2ad0d0fe7ba814127a9a?d=mp&s=160"},"body":"My project has an \"about\" page that lists the version.  I understand why\ngit doesn't do keyword expansion, but I'm wondering if there's a\nrecommended best practice for keeping that up to date.\n\n-- \nD. Stuart Freeman\nGeorgia Institute of Technology\n\n\nbegin:vcard\nfn:D. Stuart Freeman\nn:Freeman;Douglas\nemail;internet:stuart.freeman@et.gatech.edu\ntel;work:(404)385-1473\nx-mozilla-html:FALSE\nversion:2.1\nend:vcard\n\n"},{"id":"80321","messageId":"20080619145413.GA18563@diana.vm.bytemark.co.uk","threadId":"14038","inReplyTo":"485A6E03.6090509@et.gatech.edu","subject":"Re: Best practice question","fromName":"Karl Hasselström","fromEmail":"kha@treskal.com","sentAt":"2008-06-19T14:54:13Z","receivedAt":"2008-06-19T14:54:13Z","isPatch":false,"sender":{"key":"kha@treskal.com","avatar":"https://gravatar.com/avatar/f0120c734b5279b345075a28521e1ac66acb20c9913ffe9bf6ae97e53f7f3f13?d=mp&s=160"},"body":"On 2008-06-19 10:32:35 -0400, D. Stuart Freeman wrote:\n\n> My project has an \"about\" page that lists the version. I understand\n> why git doesn't do keyword expansion, but I'm wondering if there's a\n> recommended best practice for keeping that up to date.\n\nUsually when people ask this question on this list, the recommendation\nis to have the build system generate a suitable version string. Look\nat how git's own built-in version string is generated, for example.\n(The GIT-VERSION-GEN script.)\n\n-- \nKarl Hasselström, kha@treskal.com\n      www.treskal.com/kalle\n"},{"id":"80323","messageId":"8aa486160806190840m697ac1en3214626a56014be1@mail.gmail.com","threadId":"14038","inReplyTo":"485A6E03.6090509@et.gatech.edu","subject":"Re: Best practice question","fromName":"Santi Béjar","fromEmail":"sbejar@gmail.com","sentAt":"2008-06-19T15:40:10Z","receivedAt":"2008-06-19T15:40:10Z","isPatch":false,"sender":{"key":"santi@agolina.net","avatar":null},"body":"On Thu, Jun 19, 2008 at 16:32, D. Stuart Freeman\n<stuart.freeman@et.gatech.edu> wrote:\n> My project has an \"about\" page that lists the version.  I understand why\n> git doesn't do keyword expansion, but I'm wondering if there's a\n> recommended best practice for keeping that up to date.\n\nYou can look at how git does it:\nIt generates a GIT-VERSION-FILE with:\n\nhttp://git.kernel.org/?p=git/git.git;a=blob;f=GIT-VERSION-GEN;hb=HEAD\n\nand reads it in the Makefile. Or you could generate a version.h file.\n\nSanti\n"},{"id":"80330","messageId":"32541b130806190939t2a26c6f7j987eb1c679d53b3a@mail.gmail.com","threadId":"14038","inReplyTo":"485A6E03.6090509@et.gatech.edu","subject":"Re: Best practice question","fromName":"Avery Pennarun","fromEmail":"apenwarr@gmail.com","sentAt":"2008-06-19T16:39:19Z","receivedAt":"2008-06-19T16:39:19Z","isPatch":false,"sender":{"key":"apenwarr@gmail.com","avatar":"https://avatars.githubusercontent.com/u/20592?v=4"},"body":"On 6/19/08, D. Stuart Freeman <stuart.freeman@et.gatech.edu> wrote:\n> My project has an \"about\" page that lists the version.  I understand why\n>  git doesn't do keyword expansion, but I'm wondering if there's a\n>  recommended best practice for keeping that up to date.\n\nIf you compile git yourself and run \"git --version\", it contains the\ncurrent version number.  You may want to do it the same way.\n\nSee also the \"git-describe\" command.\n\nHave fun,\n\nAvery\n"}]}