Re: git-push branch confusion caused by user mistake

2017-03-13 Thread Phil Hord
On Mon, Mar 13, 2017 at 1:55 AM Jacob Keller wrote: > On Fri, Mar 10, 2017 at 2:13 PM, Junio C Hamano wrote: > > Phil Hord writes: > >> I think git should be smarter about deducing the dest ref from the > >> source ref if the

Re: git-push branch confusion caused by user mistake

2017-03-13 Thread Jacob Keller
On Fri, Mar 10, 2017 at 2:13 PM, Junio C Hamano wrote: > Phil Hord writes: > >> I think git should be smarter about deducing the dest ref from the >> source ref if the source ref is in refs/remotes, but I'm not sure how >> far to take it. > > My knee-jerk

Re: git-push branch confusion caused by user mistake

2017-03-11 Thread Jakub Narębski
W dniu 10.03.2017 o 22:44, Phil Hord pisze: > This week a user accidentally did this: > > $ git push origin origin/master > Total 0 (delta 0), reused 0 (delta 0) > To parent.git > * [new branch] origin/master -> origin/master > > He saw his mistake when the "new branch"

Re: git-push branch confusion caused by user mistake

2017-03-10 Thread Junio C Hamano
Phil Hord writes: > I think git should be smarter about deducing the dest ref from the > source ref if the source ref is in refs/remotes, but I'm not sure how > far to take it. My knee-jerk reaction is "Don't take it anywhere". Giving a refspec from the command line is

git-push branch confusion caused by user mistake

2017-03-10 Thread Phil Hord
This week a user accidentally did this: $ git push origin origin/master Total 0 (delta 0), reused 0 (delta 0) To parent.git * [new branch] origin/master -> origin/master He saw his mistake when the "new branch" message appeared, but he was confused about how to fix it and