On Wed, May 13, 2009 at 06:25, Ramachandran, Vishwanath(IE10)
<Vishwanath.Ramachandran_at_honeywell.com> wrote:
> Hi Ryan
>
> Thanks for the reply. Please find the description in the attached word
> file was just a "workaround" which we used today to reach that.
Not everyone has (or wants to load) MS Word to read your email. Did
you get the information from someplace online?
> -----Original Message-----
> From: Ryan Schmidt [mailto:subversion-2009b_at_ryandesign.com]
> Sent: Wednesday, May 13, 2009 2:30 PM
> To: Ramachandran, Vishwanath(IE10)
> Cc: Ryan Schmidt; Campbell Allan; users_at_subversion.tigris.org
> Subject: Re: Need possibilities to set Subversion property for keyword
> expansion
>
> On May 13, 2009, at 02:36, Ramachandran, Vishwanath(IE10) wrote:
>
>> Pls confirm my assumption:
>>
>> 1 .Keyword expansion will be done on client side. (Replacing in
>> "committed" document the "placeholder" with the keywords).
>
> Yes, keyword expansion happens on the client.
>
>
>> 2. The client will do this action only if the svn property is set
>> (stored in repository). If the svn-property is not set client is not
>> doing any keyword expansion.
>
> Yes, keyword expansion will only happen if the svn:keywords property
> is set, and then only for those keywords listed in that property.
>
>
>> 3. This property can be created in different ways:
>> a.) manually (e.g. on client subversion -> property dialog -> new
>> property -> snv: keyword expansion)
>
> It's "svn:keywords". It sounds like you are describing the procedure
> for setting this property in some GUI client (perhaps TortoiseSVN).
> Of course you can also set it using the command line client with "svn
> propset svn:keywords '<list of keywords>' <file>".
>
>
>> b.) automated on client: -> if in autoprops the corresponding entries
>> are set the property will be set once the first commit happens.
>
> Basically right. I think the properties are actually set the moment
> you "svn add" the file.
>
>
>> c.) The way you proposed it -> on the server with a script which
>> checks
>> if the property is not already set -> and if not set -> set the
>> property.
>>
>> ->a.) and b.) we are doing already and we know that it works ->
>> disadvantage: For a.) -> manual work, for b.) -> all clients need
>> to get
>> the autoprops set -> which is also manual work on each client -> error
>> prone.
>
> It is not error prone if you install a pre-commit hook to reject any
> commit that does not conform to your requirements. Yes, there is a
> little manual work, but only once for each client (until you change
> your policy...)
>
>
>> -> desired would be solution c [:)]
>
> Someone else mentioned this can be done even without a server-side
> working copy, so you're welcome to implement this if you feel it's a
> better fit for you.
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2234569
>
> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2234639
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-13 12:33:38 CEST