> On Mar 3, 2016, at 12:58 AM, Jagdish Deshmukh
> wrote:
>
> ---
> Subversion Exception!
> ---
> Subversion encountered a serious problem.
> Please take the time to report this on the Subversion mailing list
> with as much information as possible
On Mar 3, 2016, at 12:50 AM, Jackie Xiao wrote:
> I’m writing a svn pre-commit hook, and I want to quit further rule checkings
> if the commit is a merge operation.
>
> I have searched online, it seems there are no way to distinguish normal
> commit from merge commit.
>
> My current way fo
Oh man, that's surely it. Thanks, folks.
Tom
On 03/03/16 21:03, jbl...@icloud.com wrote:
On Mar 3, 2016, at 12:53 PM, Philip Martin wrote:
jbl...@icloud.com writes:
On Mar 2, 2016, at 10:16 AM, txm wrote:
$ svn info /home/user/nodes/dev_5_main
svn: '/home/user/nodes' is not a wor
> On Mar 3, 2016, at 12:53 PM, Philip Martin wrote:
>
> jbl...@icloud.com writes:
>
> On Mar 2, 2016, at 10:16 AM, txm wrote:
>
> $ svn info /home/user/nodes/dev_5_main
> svn: '/home/user/nodes' is not a working copy
>
>>> On Mar 3, 2016, at 12:06 AM, txm wrote:
>>>
>>>
jbl...@icloud.com writes:
On Mar 2, 2016, at 10:16 AM, txm wrote:
$ svn info /home/user/nodes/dev_5_main
svn: '/home/user/nodes' is not a working copy
>> On Mar 3, 2016, at 12:06 AM, txm wrote:
>>
>> Sorry,
>>
>> svn, version 1.6.6 (r40053)
>> svn is hashed (/usr/bi
Dear list:
I'm writing a svn pre-commit hook, and I want to quit further rule checkings if
the commit is a merge operation.
I have searched online, it seems there are no way to distinguish normal commit
from merge commit.
My current way for handling this is very clumsy, get the changed list fr
---
Subversion Exception!
---
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
with as much information as possible about what
you were trying to do.
But please first search the mailing list
>>> On Mar 2, 2016, at 10:16 AM, txm wrote:
>>>
>>> Hello,
>>>
>>> I am confused and frustrated by this:
>>>
>>>$ pwd
>>>/home/user/nodes/dev_5_main
>>>
>>>$ svn info /home/user/nodes/dev_5_main
>>>svn: '/home/user/nodes' is not a working copy
>>>
>>>$ svn info .
>>>Pa
> -Original Message-
> From: Johan Corveleyn [mailto:jcor...@gmail.com]
> Sent: donderdag 3 maart 2016 09:30
> To: webster.br...@rogers.com
> Cc: users@subversion.apache.org
> Subject: Re: Weird Behaviour: Files reverted that didn't show up in a status
> --
> no-ignore
>
> On Wed, Mar 2
On Wed, Mar 2, 2016 at 9:53 PM, wrote:
> We are running VisualSVN 1.9.3 server on a Windows box and a user's
> workspace is on a Centos6.5 Linux box.
> He had just done a "svn update" and the build failed. No conflicts as far
> as I can tell. The "svn status" showed the build artifacts and his
10 matches
Mail list logo