Re: [PATCH 6/7] sha1_name: prepare to introduce AT_KIND_PUSH

2013-05-24 Thread Ramkumar Ramachandra
Felipe Contreras wrote: > git push branch@{push} > > Is not clear at all: push push of branch? We can pick the name later. I had to pick a name to write code, and that happens to be @{push}. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@

Re: [PATCH 6/7] sha1_name: prepare to introduce AT_KIND_PUSH

2013-05-24 Thread Felipe Contreras
On Thu, May 23, 2013 at 10:12 AM, Ramkumar Ramachandra wrote: > Introduce an AT_KIND_PUSH to be represented as "@{p[ush]}". Determine > it using branch.remote.push_refspec. I think the semantics of this don't make any sense. git push branch@{upstream} Is very clear: push upstream of branch.

[PATCH 6/7] sha1_name: prepare to introduce AT_KIND_PUSH

2013-05-23 Thread Ramkumar Ramachandra
Introduce an AT_KIND_PUSH to be represented as "@{p[ush]}". Determine it using branch.remote.push_refspec. Signed-off-by: Ramkumar Ramachandra --- sha1_name.c | 13 +++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/sha1_name.c b/sha1_name.c index 106716e..5f6958b 1006