's the
intended behavior, then why doesn't it throw an error message at the user when
using these two flags together instead of silently ignoring
"--ignore-properties"?
Please consider either adding this "filtering", or an error message in future
releases.
BR,
Chris
On Mon, 3/23/15, Julian Foad wrote:
Subject: Re: diff --summarize --ignore-properties
To: "Chris"
Cc: "dev"
Date: Monday, March 23, 2015, 12:26 PM
Hi Chris.
On 23 March 2015 at 09:43,
Chris wrote:
> searching fo
I posted this on the users list, but I'm confident that this is a bug.
Background:
For a while now (off and on for over a year, but more frequently in the
last 6+ months) we've been having problems with svn "crashing", yet
there's no error in the log file. In talking to someone the users list
On 11/8/2010 8:54 PM, Paul Burba wrote:
On Mon, Nov 8, 2010 at 8:28 PM, Chris Tashjian wrote:
Paul - 1 more question. What happens when you run additional blame -g
commands? Does the memory usage keep growing until it runs out of memory or
will it cap itself at some point? In my tests it
Hi Julian,
I've made the changes as you suggested.
Regards,
Chris
[[[
Make it easy to (re)run specific tests on windows by adding a --test/-t
option. The tests can also specify specific test number(s) to run.
* win-tests.py
(_usage_exit): Add the --test/-t option to the help.
(tests_t
Adding to the list of people experiencing this issue.
Using Windows 7 x64 trying to connect to a repo on unfuddle.com.
Hi,
This patch adds the ability to specify one or more tests to run on Windows.
The --test option takes the name of the test executable.
e.g. win-tests.py --release --test=basic_tests.py -t client-test.exe
Regards
Chris
[[[
Make it easy to (re)run specific tests on windows by adding a --test
- "Gavin 'Beau' Baumanis" wrote:
> Hi Chris,
>
> Just following up your patch submission and checking if you were going
> to be following-up on the suggestions provided by Bert and Daniel?
>
> Gavin.
>
Hi Gavin,
I'll be posting an upda
t.exe"/"_tests.py" part). It can also take test number(s) to be run in
those tests by appending #NUM to the test name.
e.g. win-tests.py --release --test=basic_tests.py -t client
win-tests.py --release --test=basic_tests.py#4 -t client#2,4-6
Regards
Chris
[[[
Make it easy to (re)r
I encountered the following assert failure while doing the first SVN update
after upgrading my working copy using v1.7.1 (I was previously using v1.6.16).
In file
'D:\Development\SVN\Releases\TortoiseSVN-1.7.1\ext\subversion\subversion\libsvn_wc\update_editor.c'
line 1582: assertion failed (actio
xternal-dir/*.pyc' ./
>
> (which nicely parallels the fact that svn:externals can be set at
> a non-immediate parent)
Yep, +1, this would be cool. Any pointers in the right direction and I might
even be able to dust off some of my C skillz to make it happen (not anytime
soon, but would be willing to try). Where would I even start?
Thanks for any help.
Cheers,
Chris
Hi Greg,
> Please vote:
>
> [X] +1 Graduation
> [ ] -1 Hold, and continue incubating
>
(non-binding)
Cheers,
Chris
¿
Long time coming, Greg. Congrats to the SVN community!
Cheers,
Chris
On 2/17/10 1:16 PM, "Greg Stein" wrote:
Hi all,
The ASF Board just voted to approve the graduation of Subversion from
the Incubator. We are now an official project of the Apache Software
Foundation!
Go forth
13 matches
Mail list logo