Re: post-commit hook stderr not marshalled back

2010-01-21 Thread Bastien Semene
Giulio Troccoli a écrit : Linedata Services (UK) Ltd Registered Office: Bishopsgate Court, 4-12 Norton Folgate, London, E1 6DB Registered in England and Wales No 3027851VAT Reg No 778499447 -Original Message- From: Bastien Semene [mailto:bsem...@cyanide-studio.com] Sent: 21 J

RE: post-commit hook stderr not marshalled back

2010-01-21 Thread Giulio Troccoli
> Linedata Services (UK) Ltd Registered Office: Bishopsgate Court, 4-12 Norton Folgate, London, E1 6DB Registered in England and Wales No 3027851VAT Reg No 778499447 -Original Message- > From: Bastien Semene [mailto:bsem...@cyanide-studio.com] > Sent: 21 January 2010 14:07 > To: us

Re: post-commit hook stderr not marshalled back

2010-01-21 Thread Bastien Semene
Yes, it should be. Actually everything works in a perfect world in my example, 99.9% of the time the commiter should see the same number. But if something goes wrong during the update the commiter should be aware of it asap. I can handle more problems later in the script (or in another script as

Re: post-commit hook stderr not marshalled back

2010-01-21 Thread Andy Levy
On Thu, Jan 21, 2010 at 09:06, Bastien Semene wrote: > Hi list, > > I currently can't get the stderr output of the post-commit hook script back > to the client. > > The goal of this part of this post-commit hook script is to update a > specific working copy when someone commit on a particular fold