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

Re: perl hooks

From: David Weintraub <qazwart_at_gmail.com>
Date: Wed, 17 Dec 2008 16:11:14 -0500

Please make sure you send replies to the entire list...

I assume you are talking about "svnlook cat" and not "svnlook cut".

Where are you outputting this file? If you are sending the output to a
program that may use HTML commands, you might find that it recognizes
the "<" and ">" as HTML tag markers and ignore their contents. If this
is the case, you must convert "<" to "&lt;" before sending it to the
program and ">" to &gt;".

There shouldn't be any reason you to have this problem if you are
printing the output to a file or to the console window.

On Wed, Dec 17, 2008 at 9:04 AM, Ilan Yaniv <Ilan.Yaniv_at_timetoknow.org> wrote:
> Hi David,
> Everything worked fine.
> I have moved on with the exe (originated from perl) and I output info
> into STDERR.
> But now I want to see the file content that I have just commited.
> So I am running the command:
> Svnlook cut <REPOS_PATH> <FILE_PATH>
> And I got the output wrong.
> This is an xml file, and whenever I get lines with Tags
> eg.<a>aaa</aaa>
> the line is ignored
> WHY?
> -----Original Message-----
> From: David Weintraub [mailto:qazwart_at_gmail.com]
> Sent: Tuesday, December 16, 2008 7:57 PM
> To: Ilan Yaniv
> Subject: Re: perl hooks
> Ilan:
> Please don't send out so many emails to the list on the same topic.
> This is a volunteer list, and most people who respond are probably
> based in the U.S., so you might have to wait a few hours until you get
> an answer.
> If you send out repeated queries on the same topic, you'll find your
> emails being considered spam, and going directly into people's
> trashcan.
> I've answered this query from another email you sent out. Subversion
> server side pre-commit hooks don't communicate with the client unless
> you exit the pre-commit hook script with an exit code other than zero.
> In that case, it will send the user what was printed out via STDERR,
> and stop the commit operation.
> If you merely want to send users information, and not want to stop a
> commit, consider a post-commit hook. You can also use email or IM
> messaging to let users know information during the transaction too.
> Take a look at the NET::AIM Perl extension:
> http://search.cpan.org/~aryeh/Net-AIM-1.22/AIM.pm.
> I also mentioned in my other email about the PATHEXT environment
> variable. Adding .pl to this will allow you to treat Perl scripts on
> the same level as Batch and executables.
> On Tue, Dec 16, 2008 at 6:47 AM, Ilan Yaniv <Ilan.Yaniv_at_timetoknow.org>
> wrote:
>> So here is the thing.
>> I have a perl script. It is running OK from command line
>> But when I execute the script from hook (I run in command line svn
>> commit...) nothing happens.
>> Why ?????
>> Ilan Yaniv
>> Configuration Management
>> Phone: 03-7534333 ext. 5873
>> Ilan.Yaniv_at_timetoknow.org
> --
> --
> David Weintraub
> qazwart_at_gmail.com

David Weintraub
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2008-12-17 22:12:03 CET

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