I'll look at that, thanks. I'm finished now for the rest of the year (!),
so it'll be January before I post anything.
Leo
On 12 December 2014 at 15:54, Philip Martin
wrote:
> leo ponton writes:
>
> > We're using the CollabNet 1.8.10 release, so fairly up to date.
> > I've now reconfigured the
leo ponton writes:
> We're using the CollabNet 1.8.10 release, so fairly up to date.
> I've now reconfigured the hooks to run a svn diff in the post-commit. It's
> just a little clumsy as I have to construct the repo url from bits. It also
> means that the commit cannot be interrupted if the patc
We're using the CollabNet 1.8.10 release, so fairly up to date.
I've now reconfigured the hooks to run a svn diff in the post-commit. It's
just a little clumsy as I have to construct the repo url from bits. It also
means that the commit cannot be interrupted if the patch generation fails.
Leo
On
On Fri, Dec 12, 2014 at 11:07 AM, leo ponton wrote:
> In a windows pre-commit hook batch file I'm using svnlook diff to generate
> patch files to apply to an isolated repository:
>
>
>
> svnlook diff -t%TXN% %REPOS%\ > tmp\%FILENAME%
>
>
>
> Most times it works, but occassionally, it'll trunca
In a windows pre-commit hook batch file I'm using svnlook diff to generate
patch files to apply to an isolated repository:
svnlook diff -t%TXN% %REPOS%\ > tmp\%FILENAME%
Most times it works, but occassionally, it'll truncate the code in the
diff, e.g.
+
+
