2016 2:36 PM, Eric Johnson wrote:
Hi Amad
On 11/1/16 10:26 AM, CM Analyst wrote:
> Hello,
> In our environment, there is a need to identify one or more set of
> files with a custom attribute. I expect SVN properties is the way to go?
> For a given set of .exes, I want to attach a
tie
disparate components together using the property feature.
Perhaps that's not possible.
On Tuesday, November 1, 2016 2:36 PM, Eric Johnson wrote:
Hi Amad
On 11/1/16 10:26 AM, CM Analyst wrote:
> Hello,
> In our environment, there is a need to identify one or more set of
Hi Amad
On 11/1/16 10:26 AM, CM Analyst wrote:
Hello,
In our environment, there is a need to identify one or more set of
files with a custom attribute. I expect SVN properties is the way to go?
For a given set of .exes, I want to attach an attribute using the SVN
property called "RC: Re
Hello, In our environment, there is a need to identify one or more set of
files witha custom attribute. I expect SVN properties is the way to go? For a
given set of .exes, I want to attach anattribute using the SVN property called
"RC: Release Candidate". My questions: 1) Is this
e to the problem.
> But at the end svnsync writes a message NOTE: Normalized svn:* properties to
> LF line endings .
> Is it possible to disable this behavior or to undo this normalization?
> After that we have no working our Issue tracker properties on client side
> (tortoise svn) .
Johan Corveleyn napsal(a):
On Wed, May 21, 2014 at 10:02 AM, Aleš Vojáček wrote:
Hi all,
we are trying to upgrade our svn repo from 1.6 to 1.8.9 using svnsync.
But at the end svnsync writes a message NOTE: Normalized svn:* properties to
LF line endings .
Is it possible to disable this behavior or to undo
ing svnsync.
>>> But at the end svnsync writes a message NOTE: Normalized svn:* properties
>>> to
>>> LF line endings .
>>> Is it possible to disable this behavior or to undo this normalization?
>>> After that we have no working our Issue tracker pr
On Wed, May 21, 2014 at 10:02 AM, Aleš Vojáček wrote:
> Hi all,
> we are trying to upgrade our svn repo from 1.6 to 1.8.9 using svnsync.
> But at the end svnsync writes a message NOTE: Normalized svn:* properties to
> LF line endings .
> Is it possible to disable this behavior
Hi all,
we are trying to upgrade our svn repo from 1.6 to 1.8.9 using svnsync.
But at the end svnsync writes a message NOTE: Normalized svn:*
properties to LF line endings .
Is it possible to disable this behavior or to undo this normalization?
After that we have no working our Issue tracker
<mailto:users@subversion.apache.org>
Subject: Server-side enforcement of SVN properties
Hello all,
I have a Subversion server and a bunch of Windows clients
accessing it with TortoiseSVN via http protocol (Apache
mod_dav_svn). I wa
gt;
>> -Original Message-
>>
>>
>> From: Leonid Zeitlin [mailto:l...@csltd.com.ua]
>>> Sent: 13 April 2010 10:03
>>> To: users@subversion.apache.org
>>> Subject: Server-side enforcement of SVN properties
>>>
>>> Hello a
]
Sent: 13 April 2010 10:03
To: users@subversion.apache.org
Subject: Server-side enforcement of SVN properties
Hello all,
I have a Subversion server and a bunch of Windows clients
accessing it with TortoiseSVN via http protocol (Apache
mod_dav_svn). I want a certain Subversion property (namely
t; To: users@subversion.apache.org
> Subject: Server-side enforcement of SVN properties
>
> Hello all,
> I have a Subversion server and a bunch of Windows clients
> accessing it with TortoiseSVN via http protocol (Apache
> mod_dav_svn). I want a certain Subversion property (namely,
>
Hello all,
I have a Subversion server and a bunch of Windows clients accessing it
with TortoiseSVN via http protocol (Apache mod_dav_svn). I want a
certain Subversion property (namely, svn:needs-lock) to be set on all
new files with certain extension. I know this can be done with
auto-props se
On Jan 27, 2010, at 18:29, Alan Leung wrote:
> We are importing code from a vendor SVN repository into a branch in our
> SVN repository. If necessary we may make changes to this code and merge
> with future releases of the vendor code.
>
> During this import, we are trying to
.
During this import, we are trying to retain the SVN properties (e.g.
svn:ignore, svn:keywords, svn:eol-style) in the copy in our SVN
repository. The svn import command skips .svn directories during import
into our SVN repository (despite setting --no-ignore flag).
Other relevant information
16 matches
Mail list logo
