On Thu, 24 Oct 2013 12:25:00 -0400
lingfei ouyang <oylf1...@gmail.com> wrote:

> The difference between the previous one are:
> 
> 1. previous one is only for hooks that checking the commit commend ...
> 2. and this new one we are trying to get more in details on
> integration with Version One, so which means when developers commit
> the changes into git, it will integrate with VersionOne and search
> for VersionOne defect#, and if it find one and it do had correct
> product versions, then this commit successful, otherwise, it fire
> this hooks to reject the commit.
> 
> I'm sorry for unclear question that I had asked.

No, that was pretty clear.  Here's why I'm asking what's really
different between (1) and (2): in the original thread I outlined how to
get hold on the commit graph that has been received (and for which the
post-receive hook is called) and how to traverse it.  So, in my opinion,
the task at hand changed from "walk the received commit graph looking
for a commit message containing the specific text" to "walk the
received commit graph looking for a commit message containing the
specific text, and once it was found, query an external service with
this text".  Am I wrong?

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to