Trying to make things a bit more clean… @John Fisher, you (and maybe your boss) might want to read [1] which somewhat explains git’s private parts, and how exactly it works. Not the most complete list (to be honest, I’ve seen a better one *somewhere*, I just lost the link :( Anyways, I hope it sheds some light and helps us understand each other…
[1] http://wildlyinaccurate.com/a-hackers-guide-to-git On 11 June 2014 21:42, Dale R. Worley <wor...@alum.mit.edu> wrote: >> From: John Fisher <fishook2...@gmail.com> >> >> [...] >> [1:text/plain Hide]> *but that output does not agree with git log!* > > I am totally lost what you're talking about. > > "git log" lists *commits* and their SHAs. You say you entered "git > log rmapi_bcmxlat.c" and you seem to expect it to contain the SHAs of > (versions of) rmapi_bcmxlat.c. But it won't do that, because "git > log" lists *commits*, in this case, the commits that change the named > file. > > Dale > > -- > 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/d/optout. -- 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/d/optout.
