Re: branch..pushremote not working with push.default simple or upstream

2013-06-07 Thread Junio C Hamano
Ramkumar Ramachandra writes: > Junio C Hamano wrote: >> This shows the "triangular" support in 1.8.3 is only half-finished; >> the other half was discussed a few weeks ago ($gmane/224604) > > I intentionally omitted that detail, because it is not directly > related to this bug. We have to fix th

Re: branch..pushremote not working with push.default simple or upstream

2013-06-07 Thread Ramkumar Ramachandra
Leandro Lucarella wrote: > I might try to just switch to current, I feel more comfortable with > simple because I feel is safer to explicitly set the upstream branch, > but is true that most of the time is not necessary. Be more experimental! Use the lesser-known features, and tell us about break

Re: branch..pushremote not working with push.default simple or upstream

2013-06-07 Thread Leandro Lucarella
On Fri, Jun 07, 2013 at 10:27:58PM +0530, Ramkumar Ramachandra wrote: > Leandro Lucarella wrote: > > Thanks for the detailed explanations, I think this would cover my use > > case. Just for clarification, here are some more details on this use > > case, which I think is becoming very popular among

Re: branch..pushremote not working with push.default simple or upstream

2013-06-07 Thread Ramkumar Ramachandra
Leandro Lucarella wrote: > Thanks for the detailed explanations, I think this would cover my use > case. Just for clarification, here are some more details on this use > case, which I think is becoming very popular among github users. > We have a "blessed" repository (upstream in my case) and only

Re: branch..pushremote not working with push.default simple or upstream

2013-06-07 Thread Ramkumar Ramachandra
Junio C Hamano wrote: > This shows the "triangular" support in 1.8.3 is only half-finished; > the other half was discussed a few weeks ago ($gmane/224604) I intentionally omitted that detail, because it is not directly related to this bug. We have to fix the existing simple and upstream, whether

Re: branch..pushremote not working with push.default simple or upstream

2013-06-07 Thread Leandro Lucarella
On Fri, Jun 07, 2013 at 08:47:59AM -0700, Junio C Hamano wrote: > When branch.$name.push mechanism is introduced and the user uses it, > then "upstream", "simple", or any other setting for that matter > would be ignored. With > > [branch "master"] > remote = upstream >

Re: branch..pushremote not working with push.default simple or upstream

2013-06-07 Thread Junio C Hamano
Ramkumar Ramachandra writes: > [+CC: jc, jk] > > Leandro Lucarella wrote: >> I changed branch.master.remote to upstream and set >> branch.master.pushremote to origin, but when I do I git push I get an >> error: >> >> $ git push --dry-run --verbose >> fatal: You are pushing to remote 'origin', whi

Re: branch..pushremote not working with push.default simple or upstream

2013-06-07 Thread Ramkumar Ramachandra
[+CC: jc, jk] Leandro Lucarella wrote: > I changed branch.master.remote to upstream and set > branch.master.pushremote to origin, but when I do I git push I get an > error: > > $ git push --dry-run --verbose > fatal: You are pushing to remote 'origin', which is not the upstream of > your current b

branch..pushremote not working with push.default simple or upstream

2013-06-07 Thread Leandro Lucarella
Hi, I tried to use the new Git feature to push by default to a different remote you normally pull but I had some problems. I asked in the #git IRC channel and been told it looks like a bug and to report it here. I have 2 remotes, origin and upstream. origin is my private fork (and I can push to it