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?
> for name/value pairs.
> C. Michael Pilato <cmpilato_at_collab.net>
> CollabNet <> www.collab.net <> Distributed Development On Demand
Received on 2012-02-24 04:25:15 CET