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

Re: Calculating major.minor.patch from commit hash

From
MVMartin Vejnár <vejnar.martin@gmail.com>
Date
Feb 13, 2020, 14:54 UTC
Message-ID
<CAJFfRmt3w60Yq+HS9oVmGtfPMzLeKzFSnkwS7v4_xe+eEWSxzw@mail.gmail.com>
In-Reply-To
<014f01d5e27c$5f5166d0$1df43470$@nexbridge.com>

On Thu, Feb 13, 2020 at 3:46 PM Randall S. Becker <rsbecker@nexbridge.com> wrote:

> You should consider using annotated tags and the git describe command to derive your release number. [...]

I'd like to avoid tags in this case, because a new tag/deletion of a tag could change the hash->version mapping and I'd like that to be stable.

Previous: Randall S. BeckerNext: brian m. carlson
Message 3 of 4 in “Calculating major.minor.patch from commit hash”
  1. Martin VejnárFeb 13, 2020
  2. Randall S. BeckerFeb 13, 2020
  3. Martin VejnárFeb 13, 2020
  4. brian m. carlsonFeb 14, 2020

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.