[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: New SHA1 property for nodes returned 'svn ls --xml' invocations.

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Sun, 25 Sep 2016 07:02:23 +0000

Paul Hammant wrote on Sat, Sep 24, 2016 at 08:36:37 -0400:
> More info: the technology I'm playing with doesn't do a svn checkout, but
> instead monitors the the repo via 'svn ls' (via polling). It is easiest to
> hit up the root note and ask for a sha1, then walk the tree (remotely) to
> get the actually changes nodes deeper in the tree. Sure, the revision
> integer is there too - but I need to compare to a *local* representation of
> the same tree that's not under subversion control, and I'll have to
> calculate SHA1 of the resource immediately after bringing it down from the
> server (rather that just trusting the server's version).

Can you explain more about your use-case? We already have a solution
for monitoring repository-side changes (svnpubsub, in tools/) and for
determining which files are different in a local worktree to in the
repository ('svn diff -r HEAD', 'svn status -u').


Received on 2016-09-25 09:03:42 CEST

This is an archived mail posted to the Subversion Dev mailing list.