On Thu, Aug 4, 2016 at 10:50 AM, Ed Greenberg <e...@greenberg.org> wrote: > On 08/04/2016 01:28 PM, Junio C Hamano wrote: >> >> ... indicates that you are not pushing to update the remote >> repository correctly. Once you get that part working correctly, >> after you push at the end of the session, you should be able to do >> "git reset" at the other side to tell Git to notice that the updated >> working tree files that were transferred behind its back are now in >> sync with what is supposed to be checked out. > > If this is the case, why do my fresh clones contain the most recent commit?
Exactly. Why does your "push" not result in "git log" to show the most recent commit? Once you solve that, "git reset" would do the right thing, I would think, just like a fresh clone shows the latest. The thing is, that I didn't quite find out what your "push" is doing wrong in your original message. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
