From: Junio C Hamano <gitster@pobox.com>
To: Philip Oakley <philipoakley@iee.org>
Cc: GitList <git@vger.kernel.org>
Subject: Re: [RFC/PATCH 0/2] Test the Git version string
Date: Sun, 14 Apr 2013 12:22:17 -0700 [thread overview]
Message-ID: <7v8v4k6hp2.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1365949646-1988-1-git-send-email-philipoakley@iee.org> (Philip Oakley's message of "Sun, 14 Apr 2013 15:27:24 +0100")
Philip Oakley <philipoakley@iee.org> writes:
> 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?
next prev parent reply other threads:[~2013-04-14 19:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-14 14:27 [RFC/PATCH 0/2] Test the Git version string Philip Oakley
2013-04-14 14:27 ` [RFC/PATCH 1/2] test git " Philip Oakley
2013-04-14 14:27 ` [RFC/PATCH 2/2] Doc: State the exact " Philip Oakley
2013-04-14 19:22 ` Junio C Hamano [this message]
2013-04-14 21:26 ` [RFC/PATCH 0/2] Test the Git " Philip Oakley
2013-04-15 1:39 ` Junio C Hamano
2013-04-16 7:25 ` Philip Oakley
2013-04-16 18:12 ` Junio C Hamano
2013-04-16 18:24 ` David Aguilar
2013-04-16 19:02 ` Junio C Hamano
2013-04-16 21:22 ` Philip Oakley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v8v4k6hp2.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).