Re: Website spelling correction

2018-01-24 Thread Daniel Shahaf
Nathan Hartman wrote on Wed, 24 Jan 2018 10:15 -0500: > The page at: > https://subversion.apache.org/docs/community-guide/conventions.html > > has the text "Variadic arugment lists" in a section heading and link > to that section. That should be corrected to "Variadic argument > lists." Thanks,

Website spelling correction

2018-01-24 Thread Nathan Hartman
Hi all, The page at: https://subversion.apache.org/docs/community-guide/conventions.html has the text "Variadic arugment lists" in a section heading and link to that section. That should be corrected to "Variadic argument lists." Where is the appropriate place to contribute website corrections?

Re: File and folder names corrupted when importing from CVS using cvs2svn

2018-01-24 Thread Branko Čibej
On 24.01.2018 14:11, Nico Kadel-Garcia wrote: > On Thu, Jan 18, 2018 at 6:55 PM, Daniel Shahaf > wrote: >> Andreas Krey wrote on Thu, 18 Jan 2018 19:14 +0100: >>> svndumping, filtering and reloading may fix the file names for >>> all revisions, but I have no idea how the

Re: File and folder names corrupted when importing from CVS using cvs2svn

2018-01-24 Thread Nico Kadel-Garcia
On Thu, Jan 18, 2018 at 6:55 PM, Daniel Shahaf wrote: > Andreas Krey wrote on Thu, 18 Jan 2018 19:14 +0100: >> svndumping, filtering and reloading may fix the file names for >> all revisions, but I have no idea how the client sandboxes >> will react to that. > > The term

Re: Problem with authorized user and SVN access

2018-01-24 Thread Stefan Sperling
On Wed, Jan 24, 2018 at 11:05:40AM +0100, Torsten Krah wrote: > Some more news about that, debugged that a little bit further and imho i > think its a bug in the module code of access_checker - or there are > assumptions made which do not hold in my usecase - at least its unclear > to me why its

Re: Problem with authorized user and SVN access

2018-01-24 Thread Torsten Krah
Some more news about that, debugged that a little bit further and imho i think its a bug in the module code of access_checker - or there are assumptions made which do not hold in my usecase - at least its unclear to me why its done that way, maybe someone can give some input. The problem is that