Zeeshan Qureshi wrote: >>>> Zeeshan Qureshi wrote: >>>>> 3. then i added 1 new line to both closing.txt and file.txt >>>>> 4. i added the file closing.txt to the staging are by running 'git >>>>> add closing.txt' >>>>> 5. now i ran 'git checkout' (by mistake) [...] >>>>> 7. Now when i run 'git commit -m "closing again"', the change is not >>>>> committed even though i get a new commit id. >>>>> >>>>> The output of 'git log -p' is this (as you can clearly see, there >>>>> are new commits but no change has been recorded) [...] > I did the test again on the Solaris machine, and encountered the same problem. > > I am on a Sun Blade 1500 machine running Solaris 10. Since this seems to be hard to replicate without blastwave, I would suggest reporting it through the blastwave forum. Thanks, and good luck. -- 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