Except the ENV is *completely* cleared.
On 6/27/07, David Kastrup <dak@gnu.org> wrote:
> Karl Fogel <kfogel@red-bean.com> writes:
>
> > Markus Kuhn <Markus.Kuhn@cl.cam.ac.uk> writes:
> >> Is there any way that I can pass from the "svn commit" command line some
> >> command-line arguments to the post-commit hook script? (This would be
> >> extremely useful for some types of workflows involving post-commit
> >> activity.)
> >
> > Unfortunately no. You could use some kind of workaround in which you
> > set properties on the files being committed -- the pre- and
> > post-commit hooks can certainly examine properties. But there's no
> > facility for passing the hooks arbitrary data outside of what's being
> > committed.
> >
> > If you describe your workflows in more detail, we may be able to
> > figure out a solution that will work.
>
> Well, there is always a way to pass from the "svn commit commandline":
>
> POSTCOMMIT="my post commit options" svn commit -m ...
>
> and then use ${POSTCOMMIT} in your script...
>
> --
> David Kastrup
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 27 11:48:37 2007