Markus Schaber wrote on Fri, Feb 24, 2012 at 08:09:30 +0000:
> Hi, Daniel,
> -----Ursprüngliche Nachricht-----
> Von: Daniel Shahaf [mailto:danielsh_at_elego.de]
> >C. Michael Pilato wrote on Thu, Feb 23, 2012 at 10:48:12 -0500:
> >> On 02/23/2012 10:35 AM, Mark Phippard wrote:
> >> > On Thu, Feb 23, 2012 at 10:32 AM, Paul Burba <ptburba_at_gmail.com> wrote:
> >> >>> Why not just give users what they want? A capability string (or
> >> >>> comparable
> >> >>> mechanism) that carries the client's version number, for use with
> >> >>> start-commit hooks in allowing/denying clients which don't meet
> >> >>> the administrator's quality requirements?
> >> >>
> >> >> Mike,
> >> >>
> >> >> +1 to this enhancement. One question though, are you envisioning a
> >> >> new "capability" for each minor release or for each patch release?
> >> >> I assume the latter, but that's not entirely clear from the issue
> >> >> writeup.
> >> >
> >> > I would suggest something easily parseable like "ClientVersion-1.7.3"
> >> >
> >> > I would assume it would be a single string that contained the exact
> >> > version number and it would be up to the hook script to do something
> >> > with it.
> >> As Mark indicated, I was *not* thinking about a different capability
> >> per release -- just a single, changing one. My suggested syntax was
> >> to be "client-version=1.7.3", establishing precedent for the use of
> >> the equal sign
> >What client-version would dev builds report?
> There are two other cases we should define a rule for:
> 1) Clients like SharpSVN or TortoiseSVN, or distribution builds, when they include their own patches, or backported patches which were not officially part of that release. Especially Debian tends to prefer backporting of fixes over updating to new releases.
> 2) Clients based on alternative implementations like SvnKit (is there any other?).
Solve both by adding a "capability" for the short client name?
> Best regards
> Markus Schaber
> We software Automation.
> 3S-Smart Software Solutions GmbH
> Markus Schaber | Developer
> Memminger Str. 151 | 87439 Kempten | Germany | Tel. +49-831-54031-0 | Fax +49-831-54031-50
> Email: firstname.lastname@example.org | Web: http://www.3s-software.com
> CoDeSys internet forum: http://forum.3s-software.com
> Download CoDeSys sample projects: http://www.3s-software.com/index.shtml?sample_projects
> Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915
Received on 2012-02-24 09:53:57 CET