Philip - would the following work on your machine? I'd be +1 on the
r1496127 nomination in STATUS if the following patch were (commited to
trunk and) added to it.
In case it matters, the Python version I tested it with is 2.6.
Daniel
[[[
Follow-p to r1496127: Have the test try a date which is n
> -Original Message-
> From: phi...@apache.org [mailto:phi...@apache.org]
> Sent: donderdag 4 juli 2013 15:22
> To: comm...@subversion.apache.org
> Subject: svn commit: r1499747 -
> /subversion/trunk/subversion/tests/libsvn_wc/op-depth-test.c
>
> Author: philip
> Date: Thu Jul 4 13:22:0
oclei...@tigris.org wrote on Thu, Jul 04, 2013 at 13:43:08 -0700:
> --- Additional comments from oclei...@tigris.org Thu Jul 4 13:43:08
> -0700 2013 ---
> Thanks for [cmpilato's] feedback.
>
> I was thinking that in modern SVN the author and commit date would always
> exist
> so that wa
David Schweikert wrote on Thu, Jul 04, 2013 at 15:04:34 +0200:
> I was thinking that we could use something like a "svn update
> --readonly", where svn doesn't any check anything on the working copy,
> but just applies any changes committed since the last update.
That's a common scenario, for exam
Daniel Shahaf wrote on Thu, Jul 04, 2013 at 23:24:55 +0300:
> David Schweikert wrote on Thu, Jul 04, 2013 at 16:00:05 +0200:
> > On Thu, Jul 04, 2013 at 15:56:45 +0200, Johan Corveleyn wrote:
> > > Beware though that post-commit hooks may be running concurrently, and
> > > your 'svn update' launche
David Schweikert wrote on Thu, Jul 04, 2013 at 16:00:05 +0200:
> On Thu, Jul 04, 2013 at 15:56:45 +0200, Johan Corveleyn wrote:
> > Beware though that post-commit hooks may be running concurrently, and
> > your 'svn update' launched by $REV might still be running when $REV+1
> > tries to start 'svn
On Wed, Jul 3, 2013 at 9:13 AM, wrote:
>...
> +++ subversion/trunk/subversion/libsvn_ra_serf/util.c Wed Jul 3 13:13:49 2013
>...
> @@ -2564,12 +2575,7 @@ expat_response_handler(serf_request_t *r
>
> If an error is not present, THEN we go ahead and look for parsing
> errors.
On Thu, Jul 04, 2013 at 15:56:45 +0200, Johan Corveleyn wrote:
> Beware though that post-commit hooks may be running concurrently, and
> your 'svn update' launched by $REV might still be running when $REV+1
> tries to start 'svn update'.
I can see that it could be a problem. Not for us in this cas
On Thu, Jul 4, 2013 at 3:30 PM, David Schweikert wrote:
> Hi Johan,
>
> Thank you for your quick response!
>
> On Thu, Jul 04, 2013 at 15:18:57 +0200, Johan Corveleyn wrote:
>> > We have a svn repository with many files (more than 30'000), and need to
>> > have the HEAD version exported to a files
Hi Johan,
Thank you for your quick response!
On Thu, Jul 04, 2013 at 15:18:57 +0200, Johan Corveleyn wrote:
> > We have a svn repository with many files (more than 30'000), and need to
> > have the HEAD version exported to a filesystem, whenever a commit is
> > done.
> > ...
>
> First thing to ch
On Thu, Jul 4, 2013 at 3:04 PM, David Schweikert wrote:
> Hi,
>
> We have a svn repository with many files (more than 30'000), and need to
> have the HEAD version exported to a filesystem, whenever a commit is
> done.
>
> Currently, we have implemented this with a post-commit script that does
> a
Hi,
We have a svn repository with many files (more than 30'000), and need to
have the HEAD version exported to a filesystem, whenever a commit is
done.
Currently, we have implemented this with a post-commit script that does
a "svn update", but the script is rather slow. The reason is that "svn
up
12 matches
Mail list logo
