on passes merge to trunk.
(David, if you already said that in your response, sorry for the
duplication)
> Eric
>
>
>
> From: David Weintraub [mailto:qazw...@gmail.com]
> Sent: Wednesday, January 05, 2011 4:37 PM
> To: Berg, Eric: IT (NYK
From: David Weintraub [mailto:qazw...@gmail.com]
Sent: Wednesday, January 05, 2011 6:04 PM
To: Berg, Eric: IT (NYK)
Cc: users@subversion.apache.org
Subject: Re: Hooks That Use Perl Test::Builder Having Problems with STDERR
On Wed, Jan 5, 2011 at 5:03 PM
On Wed, Jan 5, 2011 at 5:03 PM, wrote:
> Dave, if you look into how the hooks work, basically, they are passed a
> repo path and a transaction id that, using svnlook, gives you access to
> copies of the working files, so it doesn't matter where the hooks run, nor
> is there any requirement for se
]
> Sent: Wednesday, January 05, 2011 4:37 PM
> To: Berg, Eric: IT (NYK)
> Cc: users@subversion.apache.org
> Subject: Re: Hooks That Use Perl Test::Builder Having Problems with STDERR
>
> On Wed, Jan 5, 2011 at 11:30 AM, wrote:
>>
>> I'm working on porting a fairly extensive set of C
te files in the context of a checkin transaction?
Eric
From: David Weintraub [mailto:qazw...@gmail.com]
Sent: Wednesday, January 05, 2011 4:37 PM
To: Berg, Eric: IT (NYK)
Cc: users@subversion.apache.org
Subject: Re: Hooks That Use Perl Test::Builder Having Problems
On Wed, Jan 5, 2011 at 11:30 AM, wrote:
> I'm working on porting a fairly extensive set of CVS hooks to SVN.
Okay. Stop right there. When ever someone mentions "a fairly extensive set"
of hooks, I start to think maybe most of what they want shouldn't
necessarily be hooks. When hooks are running
I'm working on porting a fairly extensive set of CVS hooks to SVN. The issue
that I'm having now is that my pre-commit hook, which runs a Perl script that
performs tests based on Test::Builder and Test::More, never show their stderr
on the console. I see it in the svn web server logs, but not
