Re: RES: Blank log messages when user has no access to specific folder

2011-05-16 Thread Daniel Shahaf
The latter. Though from memory it's a one-line change to libsvn_repos/fs-wrap.c. (no time right now or I'd give a better pointer) Ricardo Smania (Desenv) wrote on Mon, May 16, 2011 at 13:33:20 -0300: > Hello Daniel, > > Is that patch already available or it would have to be developed from scrat

Re: RES: Blank log messages when user has no access to specific folder

2011-05-16 Thread Thorsten Schöning
Guten Tag Ricardo Smania (Desenv), am Montag, 16. Mai 2011 um 18:36 schrieben Sie: > The path isn't > important, so if there is a way to show the paths and log message, > but without showing the contents, that would also be a viable solution for us. I don't think so, there is only read write acce

AW: Detect incompatible (future) workingcopy format.

2011-05-16 Thread Markus Schaber
Hi, Daniel, > Von: Daniel Shahaf [mailto:d...@daniel.shahaf.name] > > Markus Schaber wrote on Fri, May 13, 2011 at 11:20:11 +0200: > > > > What is the safest future-compatible way to check for an incompatible > > / unknown working copy format which was written by a future subversion > > version?

Subversion Installation on AIX

2011-05-16 Thread Srivastava, Vishal
Hello, I am trying to install Subversion using source on my AIX 6.1 server. I am able to execute ./configure but when I try to do make, I get the error below. Any help is appreciated. Thanks, make -- making all in apr Target "local-all" is up to date. Target "all" is up to date. -- co

Directory Tree conflicts

2011-05-16 Thread James Whitt
I'm currently dealing with a Tree conflict on a directory and I'm unable to find good information on resolving this using google (I keep finding information on files), and am wondering what hte best approach is to resolve this issue. The background is that we have two developers working on fea

RES: Blank log messages when user has no access to specific folder

2011-05-16 Thread Ricardo Smania (Desenv)
Hello Erik, What we intended when we blocked certain folders was that only a few users could see the contents of the files. The path isn't important, so if there is a way to show the paths and log message, but without showing the contents, that would also be a viable solution for us. Thank you

RES: Blank log messages when user has no access to specific folder

2011-05-16 Thread Ricardo Smania (Desenv)
Hello Daniel, Is that patch already available or it would have to be developed from scratch? Thank you, Ricardo -Mensagem original- De: Daniel Shahaf [mailto:d...@daniel.shahaf.name] Enviada em: segunda-feira, 16 de maio de 2011 12:38 Para: Ricardo Smania (Desenv) Cc: users@subversion

Re: Blank log messages when user has no access to specific folder

2011-05-16 Thread Erik Huelsmann
Hi Ricardo, On Mon, May 16, 2011 at 5:38 PM, Daniel Shahaf wrote: > Ricardo Smania (Desenv) wrote on Mon, May 16, 2011 at 11:10:34 -0300: >> Is there a way to always show the log message, even if the user can't see >> the complete list of files/folders that were commited? >> > > Not without appl

Re: Blank log messages when user has no access to specific folder

2011-05-16 Thread Daniel Shahaf
Ricardo Smania (Desenv) wrote on Mon, May 16, 2011 at 11:10:34 -0300: > Is there a way to always show the log message, even if the user can't see the > complete list of files/folders that were commited? > Not without applying a custom patch to the server. (to libsvn_repos)

Re: Detect incompatible (future) workingcopy format.

2011-05-16 Thread Daniel Shahaf
Markus Schaber wrote on Fri, May 13, 2011 at 11:20:11 +0200: > Hi, > > What is the safest future-compatible way to check for an incompatible / > unknown working copy format which was written by a future subversion > version? (e. G. WC-NG by SVN 1.7?) > > My idea was to run status with depth=empty

Blank log messages when user has no access to specific folder

2011-05-16 Thread Ricardo Smania (Desenv)
Hello, Suppose I have the following folder structure on a specific branch of a Subversion server: Product 1 Module A Module B And that a user has access to Module A but not Module B. If someone commits something to Module A, the user sees it. If someone commits to Module B, he doesn't. Th

Re: 'svn info' alternative?

2011-05-16 Thread cate
On May 15, 11:41 am, Mark Phippard wrote: > Have you looked at svnversion ? That is what it does. Yes, that works, but no code path, just the release number.

Re: Error connecting to an Apache svn server remotely

2011-05-16 Thread Ulrich Eckhardt
On Sunday 15 May 2011, Kenny Q. Zhu wrote: > I set up an apache SVN server on an Opensuse Linux server within the > university department network. Access to it from within the university > network is completely fine. One day when I tried to access from outside the > university using the linux svn c

Re: svn log --diff --depth=empty

2011-05-16 Thread Stefan Sperling
On Sun, May 15, 2011 at 08:45:15PM -0400, Joel N. Weber II wrote: > > > Would it be possible for svn log --diff to accept the same --depth > > > argument that svn diff does? An svn client I built from trunk last > > > week does not recognize --depth in conjuction with svn log --diff > > > > It no

Re: Merge, undetected tree conflict when source tree moves directory

2011-05-16 Thread Stefan Sperling
On Sun, May 15, 2011 at 07:01:55PM +0200, Paolo Compieta wrote: > (perhaps we should move to the dev-list? i'm not expert of this, i'll follow > the thread) Feel free to start a new thread on the dev list if you have a design proposal or a patch. > Said that rename=deletion++, i'd concentrate onl

Re: subversion 1.4.2

2011-05-16 Thread Eric Manceau
Thorsten Schöning a écrit : Guten Tag Eric Manceau, am Freitag, 13. Mai 2011 um 17:50 schrieben Sie: As you can see we want to gather all tests of several differents repos into a unique repo but we want to keep revision of the original repos and it seems to be hard to achieve. Maybe imposs

Re: subversion 1.4.2

2011-05-16 Thread Eric Manceau
Nico Kadel-Garcia a écrit : On Fri, May 13, 2011 at 11:32 AM, Eric Manceau wrote: Hello, I am struggling with an old version of subversion : 1.4.2 Is it safe for the repository to adopt the 1.6.16 version? It's also *wise* to upgrade, especially if your older repo is using the older