> 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
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
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
> 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
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
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
---
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