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

Re: Best practice question

From
SBSanti Béjar <sbejar@gmail.com>
Date
Jun 19, 2008, 15:40 UTC
Message-ID
<8aa486160806190840m697ac1en3214626a56014be1@mail.gmail.com>
In-Reply-To
<485A6E03.6090509@et.gatech.edu>

On Thu, Jun 19, 2008 at 16:32, D. Stuart Freeman <stuart.freeman@et.gatech.edu> 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.

You can look at how git does it: It generates a GIT-VERSION-FILE with:

http://git.kernel.org/?p=git/git.git;a=blob;f=GIT-VERSION-GEN;hb=HEAD
and reads it in the Makefile. Or you could generate a version.h file.
Santi
Previous: Karl HasselströmNext: Avery Pennarun
Message 3 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.