Hi! Thank you for examples. They guide me in good direction. But still ... On Mon, May 7, 2012 at 1:10 AM, Seth Robertson <in-gitvger@xxxxxxxx> wrote: > I'm in favor of more git hooks myself, but there is a solution to your > needs without it. Of course there is a solution. Bash is turing-complete programming language. But the question is how easy and fast it is to use something. > If you care about race conditions (and really, a lockfile(1) call can > take care of that easily enough), If git would support post-fetch hook, I would get this for free and would not have to care about race conditions. > then parse the output of fetch which will make it clear what *this* call did. Yes, because it is really easy to parse it? There are so many different things it can output and I am not sure how to find which one should I take care of and which one should I ignore. Yes, I could learn much more about git and all possible things which can happen with fetch and its output, but I am trying to avoid this. Why? Because I believe it should be much easier. I am sorry if I look a bit negative, but I am quite frustrated that for something so simple is so hard (in a time/knowledge meaning) to achieve. Of course there is a way and that if you know all git command this is maybe obvious, but why it couldn't be easier, if it is really a very simple patch to make it easier (and it was already posted to this mailing list few months ago). Mitar -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html