Re: [PATCH 0/3] Support config-based names

From: Junio C Hamano <gitster@pobox.com>
Date: Jun 12, 2007, 05:28 UTC
Message-ID: <7vbqfln3mf.fsf@assigned-by-dhcp.pobox.com>
In-Reply-To: <Pine.LNX.4.64.0706112244210.5848@iabervon.org>

Daniel Barkalow <barkalow@iabervon.org> writes:

> It can be useful to refer to commits in remotes based on their configured 
> relationship to local branches. For example, "git log HEAD^[push]..HEAD" 
> would, when pushing is set up, show what hasn't been pushed yet.

It's not like we will be adding 'push' objects and 'merge' objects, so I think HEAD^{push} (curly brace, not bracket) is good enough.

We need to see how useful this would be in practice; we would not want to add new syntax without a set of convincing use cases. At this point, it still feels as if it is a feature that was implemented only because it could, not because there was a real need.