git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Best practice question

From
Karl Hasselström <kha@treskal.com>
Date
Jun 19, 2008, 14:54 UTC
Message-ID
<20080619145413.GA18563@diana.vm.bytemark.co.uk>
In-Reply-To
<485A6E03.6090509@et.gatech.edu>
On 2008-06-19 10:32:35 -0400, D. Stuart Freeman wrote:
> My project has an "about" page that lists the version. I understand
> why git doesn't do keyword expansion, but I'm wondering if there's a
> recommended best practice for keeping that up to date.

Usually when people ask this question on this list, the recommendation is to have the build system generate a suitable version string. Look at how git's own built-in version string is generated, for example. (The GIT-VERSION-GEN script.)

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle
Previous: D. Stuart FreemanNext: Santi Béjar
Message 2 of 4 in “Best practice question”
  1. D. Stuart FreemanJun 19, 2008
  2. Karl HasselströmJun 19, 2008
  3. Santi BéjarJun 19, 2008
  4. Avery PennarunJun 19, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.