Hi, Bert,
Von: Bert Huijben [mailto:b...@qqmail.nl]
> From: Markus Schaber [mailto:m.scha...@codesys.com]
> > Von: Daniel Shahaf [mailto:danie...@elego.de]
> > > 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
> >
Ben Reser wrote on Tue, Jul 09, 2013 at 09:17:51 -0700:
> On Thu, Jul 4, 2013 at 1:32 PM, Daniel Shahaf wrote:
> > 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 anythin
On Thu, Jul 4, 2013 at 1:32 PM, Daniel Shahaf wrote:
> 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
> -Original Message-
> From: Markus Schaber [mailto:m.scha...@codesys.com]
> Sent: dinsdag 9 juli 2013 17:09
> To: Daniel Shahaf; David Schweikert
> Cc: dev@subversion.apache.org
> Subject: AW: Updatable svn export
>
> Hi,
>
> Von: Daniel Shahaf [mailto:d
Hi,
Von: Daniel Shahaf [mailto:danie...@elego.de]
> 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 committe
Hi, David,
Von: David Schweikert [mailto:da...@schweikert.ch]
> 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
> "sv
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 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
14 matches
Mail list logo
