> And why is it relevant to see/know the protocol that was used for the commit?
It's relevant because my application stores the commits paths and
allows the user to click "get history" without having to go to
subversion or TSVN. To do a "get history" on that file from the app,
I need to know what the protocol is and the full path (C:/workspace/
file1.txt is only helpful to the user who performed the commit....
svn://someserver/workspace/file1.txt can be viewed by anyone).
You said I can't get this information from a server-side hook. Can I
get it from a client-side hook?
Michael R
On Feb 17, 11:33 pm, Jean-Marc van Leerdam <j.m.van.leer..._at_gmail.com>
wrote:
> Hi,
>
> On 18 February 2010 00:46, Michael R <arphaxa..._at_gmail.com> wrote:
>
>
>
> > I'm building a post-commit client hook for Tortoise SVN. This hook
> > communicates with another application that keeps a separate record of
> > the commits that occur. When the hook is executed, I want to pass the
> > list of files that were committed to the other application. My
> > problem is that this list of files doesn't include the full protocol
> > to the file--just the local system path. How can I get TortoiseSVN to
> > give me the full protocol path (http:// or file:/// or svn://)?
>
> > For example:
> > -Now I am being handed a list of files through the PATH file
> > parameter, i.e.:
> > C:\local repository\project1\thisfile.txt
> > C:\local repository\project1\anotherfile.txt
>
> > -Because this hook could be used by people committing files either
> > through some Apache web server or through a svnserve service, I'd like
> > to be handed the full path, like this:
>
> >http://someserver/project1/thisfile.txt
> >http://someserver/project1/anotherfile.txt
>
> > or
>
> > svn://someserver/project1/thisfile.txt
> > svn://someserver/project1/anotherfile.txt
>
> > What's the best way to do this?
>
> What is the reason you are not using server side hooks for this? The
> client side will only catch your local commits done through TSVN; any
> other commit -- through different SVN clients or from other machines
> will not be caught.
>
> And why is it relevant to see/know the protocol that was used for the commit?
>
> The server side will know the repository location of the affected
> files, not the local working copy paths nor the protocol that was used
> (I think).
>
> --
> Regards,
>
> Jean-Marc
> --
> . ___
> . @@ // \\ "De Chelonian Mobile"
> . (_,\/ \_/ \ TortoiseSVN
> . \ \_/_\_/> The coolest Interface to (Sub)Version Control
> . /_/ \_\ http://tortoisesvn.net
>
> ------------------------------------------------------http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessa...
>
> To unsubscribe from this discussion, e-mail: [dev-unsubscr..._at_tortoisesvn.tigris.org].
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2448899
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-02-18 20:39:23 CET