On Wed, Jan 5, 2011 at 05:48, Jeff King <peff@xxxxxxxx> wrote: > On Tue, Jan 04, 2011 at 12:45:33PM +0300, Alexander Gladysh wrote: >> > Anyway, I'm ready to debug this issue if someone will guide me. > If adding a sleep makes it work, that sounds like a race condition in > git. But from the description of your workflow, it should be easy to > make a minimal example: > -- 8< -- > Basically, we generate random data which has a 20% chance of > being the same as what's there. When it is, we should get "not bothering > to commit", but in your error case, we would try to commit (and get "no > changes"). > But using that script, I can't replicate your problem. Can you try > running it on the same box you're having trouble with? That might at > least tell us if it's your environment or something more complex going > on. Thank you. I tried it, and, unfortunately, it does not reproduce the problem. Alexander. -- 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