Thread (4 messages) flat view 4 messages, 4 authors, 2016-08-11
  • (off-list ancestor, not in this archive)
  • Re: (unknown) · Junio C Hamano <hidden> · 2016-08-11
  • Re: (unknown) · Josef Weidendorfer <hidden> · 2016-08-11
  • Re: (unknown) · Linus Torvalds <torvalds@osdl.org> · 2016-08-11
  • Re: (unknown) · Andy Parkins <hidden> · 2016-08-11

Re: (unknown)

From: Junio C Hamano <hidden>
Date: 2016-08-11 19:47:00

Junio C Hamano [off-list ref] writes:
Andy Parkins [off-list ref] writes:
quoted
On Wednesday 2006, October 25 19:38, Junio C Hamano wrote:
quoted
quoted
I did try that, but then the branches don't appear in git branch.  I
still like that they exist.
"git branch -r" perhaps.
That's pretty good.  It makes things like

  git-log remotes/origin/master..master

A bit long winded, but it's certainly what I asked for.
"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).

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help