Re: (unknown)
- From
- Andy Parkins <andyparkins@gmail.com>
- Date
- Oct 26, 2006, 07:14 UTC
- Message-ID
- <200610260814.05957.andyparkins@gmail.com>
- In-Reply-To
- <7vwt6okpgr.fsf@assigned-by-dhcp.cox.net>
Show 14 quoted lines
> > "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