RE: pre-commit hooks does not show any output
From: Daevid Vincent <daevid_at_daevid.com>
Date: Fri, 16 May 2008 14:47:55 -0700
Here's another little trick a friend showed me to save you the hassle of
Put this at the top of your script somewhere:
# redirect all output to stderr rather than line by line
exec 1>&2
then ALL echo's will be redirected for you. J
I've also updated my script some more (find online at the same link) to
http://www.daevid.com/content/examples/snippets.php
From: prakash tiwary [mailto:prakash.tiwary_at_gmail.com]
Daevid, Hari
Regards,
On Fri, May 16, 2008 at 2:32 AM, Hari Kodungallur <hkodungallur_at_gmail.com>
On Thu, May 15, 2008 at 12:38 PM, Daevid Vincent <daevid_at_daevid.com> wrote:
Yeah, I struggled last night for several hours trying to find what would
commit-access-control.pl is part of the source distribution.
Anyways Hari, Hopefully this will save you some gray hair pulling.
The first trick that nobody mentions is that you have to redirect all output
echo "A commit log message is required." 1>&2
The documentation for pre-commit says that: "Anything printed to stderr is
[Basically, I don't understand the "(?!)" and why it is an annoyance, if the
The next thing that took me forever to figure out (and find examples on the
You are correct that we need to use SVNLOOK to get the check-in details.
Another huge issue I found is that almost all the examples are in Python! I
There are a couple of examples in bash. Other examples in the svn repository
But I believe the idea is to provide the user with information on how you
Long story short, here is what I came up with so far in the five plus hours
(I will keep it updated as I learn more and find more interesting/useful
http://www.daevid.com/content/examples/snippets.php
I think the information you provide are very useful. It is great that you
Thanks,
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.