git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Tue, 16 Apr 2013 11:12:33 -0700	[thread overview]
Message-ID: <7v8v4imjji.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <99AE5E981E2547B6A71A4D77B17167B9@PhilipOakley> (Philip Oakley's message of "Tue, 16 Apr 2013 08:25:24 +0100")

"Philip Oakley" <philipoakley@iee.org> writes:

>> What kind of benefit are you envisioning out of this?
>
> The purpose of tests is to detect mistakes and spot regressions.
>
> A change to the 'git version X.Y.z' string would be a regression, as I
> spotted earlier, as it conflicts with expectations of standard
> programmes such as git-gui.

Sorry, but I do not follow.

A released version says "git version 1.8.2.1".  In a month or so,
I'll have another one that says "git version 1.8.3".  Or I may
decide to bump in preparation for 2.0 and it may identify itself as
"git version 1.9".

Neither of which no existing "program such as git-gui" has ever
seen.

In what way is that a regression?

  reply	other threads:[~2013-04-16 18:12 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 ` [RFC/PATCH 0/2] Test the Git " Junio C Hamano
2013-04-14 21:26   ` 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 [this message]
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=7v8v4imjji.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).