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

Re: [RFC/PATCH 0/2] Test the Git version string

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 14, 2013, 19:22 UTC
Message-ID
<7v8v4k6hp2.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1365949646-1988-1-git-send-email-philipoakley@iee.org>
Philip Oakley <philipoakley@iee.org> writes:
Show 6 quoted lines
> This patch series seeks to add tests for the version string format
> and document it.
>
> The key questions to be answered are:
> * should the test be inside t0000, or somewhere else?
> * should the version string be limited to one line, <80 characters?
One line, perhaps, but I do not think any byte-limit is reasonable.

It is unreasonable to limit the form to X.Y.Z; after we hit Git 2.0, it is likely that we would go to two-decimals.

If the "parsing" is done for white/blacklist purposes, is there a need to straight-jacket the verison string format like this series?

Previous: Philip OakleyNext: Philip Oakley
Message 4 of 11 in “Test the Git version string”
  1. 0/2 Test the Git version stringPhilip Oakley, Apr 14, 2013
  2. 1/2 test git version stringPhilip Oakley, Apr 14, 2013
  3. 2/2 Doc: State the exact git version stringPhilip Oakley, Apr 14, 2013
  4. Junio C HamanoApr 14, 2013
  5. Philip OakleyApr 14, 2013
  6. Junio C HamanoApr 15, 2013
  7. Philip OakleyApr 16, 2013
  8. Junio C HamanoApr 16, 2013
  9. David AguilarApr 16, 2013
  10. Junio C HamanoApr 16, 2013
  11. Philip OakleyApr 16, 2013

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.