> > "git log remotes/origin..master" perhaps? > > > > The point being, remotes/origin when origin is a directory that > > has HEAD that points at something, it stands for > > remotes/origin/HEAD. > > Heh, I spoke too fast. > > "git log origin..master" > > If you do not have none of .git/origin, .git/refs/origin, > .git/refs/tags/origin, .git/refs/heads/origin, nor > .git/refs/remotes/origin, then .git/refs/remotes/origin/HEAD is > what "origin" means (see get_sha1_basic() in sha1_name.c). Again: you guys have thought of everything. I believe then, that my problem is that I didn't find this written anywhere - would it be useful if I were to write a Documentation/ file about commit-ish/tree-ish that covered these issues? Have I overlooked the existence of such a file already? Andy -- Dr Andy Parkins, M Eng (hons), MIEE andyparkins@gmail.com - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Thu Oct 26 17:14:19 2006
This archive was generated by hypermail 2.1.8 : 2006-10-26 17:15:12 EST