Re: svn rename adds mergeinfo property / renaming in working copy does not

Hi Stefan, On 6 November 2017 at 19:06, Stefan Sperling wrote: > On Mon, Nov 06, 2017 at 06:10:37PM +0100, Nicolai Scheer wrote: > > I cannot imagine a case where copying the mergeinfo to the new folder is > a > > wanted behaviour > > The current behaviour was implemen

svn rename adds mergeinfo property / renaming in working copy does not

Hi all, I just stumbled across a very strange behaviour. We're using a pre-commit hook, that checks if a commit involves a merge operation. If the operation does involve a merge, we force the user to use the word "merge" in the commit message. I implented this using svnlook diff --no-diff-delete

Re: Obtaining log messages for a diff

Hi Johan, On 19 May 2015 at 15:47, Nicolai Scheer wrote: > Hi Johan, > > On 18 May 2015 at 15:44, Johan Corveleyn wrote: >> >> On Mon, May 18, 2015 at 2:59 PM, Nicolai Scheer >> wrote: >> > Hi all, >> > >> > we run our su

Re: Obtaining log messages for a diff

Hi Mark, On 19 May 2015 at 15:51, Mark Phippard wrote: > On Mon, May 18, 2015 at 8:59 AM, Nicolai Scheer > wrote: >> >> Hi all, >> >> we run our subversion repository with a rather standard layout, e.g.: >> >> /trunk >> /branches/1.0.x >>

Re: Obtaining log messages for a diff

Hi Andreas, On 18 May 2015 at 19:07, Andreas Stieger wrote: > Hello, > > On 18/05/15 15:44, Johan Corveleyn wrote: >> On Mon, May 18, 2015 at 2:59 PM, Nicolai Scheer >> wrote: >>> [...] >>> Currently, I'm trying to solve a seemingly simple task, that

Re: Obtaining log messages for a diff

Hi Johan, On 18 May 2015 at 15:44, Johan Corveleyn wrote: > > On Mon, May 18, 2015 at 2:59 PM, Nicolai Scheer > wrote: > > Hi all, > > > > we run our subversion repository with a rather standard layout, e.g.: > > > > /trunk > > /branches/1.0.x > &

Obtaining log messages for a diff

Hi all, we run our subversion repository with a rather standard layout, e.g.: /trunk /branches/1.0.x /branches/1.1.x /tags/1.0.0 /tags/1.0.1 /tags/1.1.0 /tags/1.1.1 Trunk of a project gets branched to the branches folder, and tagged from there on. We enforce that every commit's message includes

Re: SVN 1.8 Kerberos Client problems

Hi! Firstly, thanks for your quick answer! On 8 July 2014 21:24, Lieven Govaerts wrote: > Hi Nico, > [...] >> >> Everything ran fine so far. I then upgraded to TSVN 1.8.7 which ships >> with svn 1.8.9 binaries. >> Now, on every repository involving action I get kerberos errors in my >> apache lo

SVN 1.8 Kerberos Client problems

Hi, I did an update to svn 1.8.9 on our server yesterday and am now running into problems whilst updating the corresponding windows client. Server details: CentOS 6.5 x64 SVN 1.8.9, compiled on my own Apache 2.2.15 Authentication using mod_auth_kerb to windows domain Client: Windows Server 2008