Re: Arguments to git hooks

On Mon, May 7, 2012 at 2:41 AM, Marcus Karlsson [off-list ref] wrote:

There are many different reasons to use hooks. If everything that a hook
could potentially need was passed to it as an argument then a lot of
data would often end up unused. Better to supply as little as possible
and only do more work when it's actually needed.

That seems like a good reason not to pass all of the data, but isn't
the file names the most primary thing somebody can ask for?

quoted

Are you suggesting me to run some plumbing command, parse the result
and get the required data ? Is there an easier way to get this done?

I wouldn't go as deep as the plumbing, I think git status --porcelain
should work just fine, the output is fairly easy to parse.

I have always wondered why 'git status --porcelain' is giving a
'plumbing' style output. Any docs on this somewhere?

-- 
Jaseem Abid
http://jaseemabid.github.com