> > We have a lot of users using Subversion under Cygwin, which means
> that
> > any files they add get marked as executable by default (and
> almost
> > always uselessly). Is there any way to disable the automatic
> setting
> > of the svn:executable property on an "svn add"?
> > The closest thing
The problem is that any file created by a non-Cygwin Windows program will show
up in Cygwin as mode 777 by default, unless you do a chmod from the Cygwin
shell afterwards. What I'm looking for is a solution that would be convenient
for the Cygwin/Windows users and not subject to the "user needs
On Fri, 27 May 2011 13:27:36 +, dar...@chaosreigns.com wrote:
> On 05/27, Bob Archer wrote:
> > I'm confused about what you are asking. Are you saying you don't want
> > subversion to expand the keywords? If so, then remove them from the
> > svn:keywords property. Any keywords not in the proper
On 05/27, Bob Archer wrote:
> I'm confused about what you are asking. Are you saying you don't want
> subversion to expand the keywords? If so, then remove them from the
> svn:keywords property. Any keywords not in the property are not expanded.
I want the expanded keyword, and the *un-expanded* k
> I'm working on some software (spamassassin) that uses the
> subversion
> keyword "$LastChangedDate$". In the same file that it's used, I
> want that
> string to appear unmodified - not expanded by subversion, exactly
> as
> "$LastChangedDate$" instead of something like "$LastChangedDate:
> 2010-
I'm working on some software (spamassassin) that uses the subversion
keyword "$LastChangedDate$". In the same file that it's used, I want that
string to appear unmodified - not expanded by subversion, exactly as
"$LastChangedDate$" instead of something like "$LastChangedDate: 2010-03-30
08:02:18 -
Bastien Semene wrote on Fri, May 27, 2011 at 15:43:15 +0200:
> What is the correct way to resolve this kind of locks problem if the
> svnadmin command doesn't want to remove locks either ?
>From memory, removing all the digest files while no server is running
should work.
> We have a lot of users using Subversion under Cygwin, which means
> that any files they add get marked as executable by default (and
> almost always uselessly). Is there any way to disable the
> automatic setting of the svn:executable property on an "svn add"?
> The closest thing I see in the ma
Le 27/05/2011 15:34, Daniel Shahaf a écrit :
Bastien Semene wrote on Fri, May 27, 2011 at 14:44:53 +0200:
Hi I have a SVN + Apache setup running on FreeBSD :
# uname -v
FreeBSD 8.1-RELEASE #0: Fri Aug 6 09:37:33 CEST 2010
# svn --version
svn, version 1.6.16 (r1073529)
compiled Apr 13 2011,
Bastien Semene wrote on Fri, May 27, 2011 at 14:44:53 +0200:
> Hi I have a SVN + Apache setup running on FreeBSD :
> # uname -v
> FreeBSD 8.1-RELEASE #0: Fri Aug 6 09:37:33 CEST 2010
> # svn --version
> svn, version 1.6.16 (r1073529)
>compiled Apr 13 2011, 09:43:52
> # httpd -v
> Server versio
Hi I have a SVN + Apache setup running on FreeBSD :
# uname -v
FreeBSD 8.1-RELEASE #0: Fri Aug 6 09:37:33 CEST 2010
# svn --version
svn, version 1.6.16 (r1073529)
compiled Apr 13 2011, 09:43:52
# httpd -v
Server version: Apache/2.2.15 (FreeBSD)
Server built: Jul 23 2010 18:16:05
Today users
> -Original Message-
> From: poona...@yahoo.com [mailto:poona...@yahoo.com]
> Sent: 27 May 2011 11:13
> To: users@subversion.apache.org
> Subject: svndumpfilter question
>
> >
> > Hi,
> >
> > I am trying to filter an svn dump to get only one module
> (ModuleA) from
> > the repository.
>
> Hi,
>
> I am trying to filter an svn dump to get only one module (ModuleA) from
> the repository. A simplistic representation of the repository is as
> follows -
>
> trunk ---
>--- ModuleA
>--- ModuleB
>--- ModuleC
>--- ModuleD
>
> tags
> --- ModuleATag1.1
>
13 matches
Mail list logo
