Re: [PATCH 4/5] branch: mention start_name in set-upstream error messages

2013-04-02 Thread Garrett Cooper
tual name we tried to use, that may help > the user figure out why it didn't work (e.g., if they gave > us the arguments in the wrong order). > > Signed-off-by: Jeff King LGTM! Reviewed-by: Garrett Cooper -- To unsubscribe from this list: send the line "unsubscr

Re: [PATCH 2/5] branch: factor out "upstream is not a branch" error messages

2013-04-02 Thread Garrett Cooper
On Tue, Apr 2, 2013 at 12:36 PM, Garrett Cooper wrote: > On Tue, Apr 2, 2013 at 12:03 PM, Jeff King wrote: >> >> This message is duplicated, and is quite long. Let's factor >> it out, which avoids the repetition and the long lines. It >> will also make futur

Re: [PATCH 2/5] branch: factor out "upstream is not a branch" error messages

2013-04-02 Thread Garrett Cooper
e at it, let's also mark it for translation. > > Signed-off-by: Jeff King LGTM! Signed-off-by: Garrett Cooper -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [BUG] inconsistent behavior with --set-upstream vs --set-upstream-to

2013-04-02 Thread Garrett Cooper
On Apr 2, 2013, at 10:23 AM, Jeff King wrote: > On Tue, Apr 02, 2013 at 10:07:01AM -0700, Garrett Cooper wrote: > >>It looks like git branch --set-upstream-to doesn't function with 1.8.1.3 >> until I run --set-upstream. Is this a known bug? > > No, but I do n

[BUG] inconsistent behavior with --set-upstream vs --set-upstream-to

2013-04-02 Thread Garrett Cooper
Hi! It looks like git branch --set-upstream-to doesn't function with 1.8.1.3 until I run --set-upstream. Is this a known bug? root@fuji-current:/usr/src # git branch --set-upstream-to origin/pjdfstest-onefs pjdfstest-onefs fatal: Not a valid object name: 'origin/pjdfstest-onefs'. root@fu