Re: [PATCH] fetch: add new fetch.default configuration

2013-06-01 Thread Felipe Contreras
On Fri, May 17, 2013 at 9:18 PM, Felipe Contreras felipe.contre...@gmail.com wrote: When the user has an upstream branch configured to track a remote tracking branch: % git checkout --set-upstream-to github/master Doing a 'git fetch' without any arguments would try to fetch 'github',

Re: [PATCH] fetch: add new fetch.default configuration

2013-05-19 Thread Felipe Contreras
On Sun, May 19, 2013 at 6:51 AM, Ramkumar Ramachandra artag...@gmail.com wrote: Felipe Contreras wrote: % git checkout fc/remote/hg-next % git rebase -i # rebase to master % git checkout fc/remote/hg-notes % git rebase -i # rebase to fc/remote/hg-next % git checkout

Re: [PATCH] fetch: add new fetch.default configuration

2013-05-19 Thread Ramkumar Ramachandra
My itch is very simple. Felipe Contreras wrote: % git checkout fc/remote/hg-next % git rebase -i # rebase to master % git pull # I want: pull from origin % git checkout fc/remote/hg-notes % git rebase -i # rebase to fc/remote/hg-next % git pull # I want: pull from ram % git checkout

Re: [PATCH] fetch: add new fetch.default configuration

2013-05-19 Thread Felipe Contreras
On Sun, May 19, 2013 at 7:26 AM, Ramkumar Ramachandra artag...@gmail.com wrote: My itch is very simple. Felipe Contreras wrote: % git checkout fc/remote/hg-next % git rebase -i # rebase to master % git pull # I want: pull from origin Then do 'git pull origin', 'fc/remote/hg-next' has

Re: [PATCH] fetch: add new fetch.default configuration

2013-05-19 Thread Ramkumar Ramachandra
Felipe Contreras wrote: % git checkout fc/remote/hg-next % git rebase -i # rebase to master % git checkout fc/remote/hg-notes % git rebase -i # rebase to fc/remote/hg-next % git checkout fc/remote/hg-gitifyhg-compat % git rebase -i # rebase to fc/remote/hg-notes So it is rebase, but

Re: [PATCH] fetch: add new fetch.default configuration

2013-05-18 Thread Ramkumar Ramachandra
Felipe Contreras felipe.contre...@gmail.com wrote: % git checkout --set-upstream-to master What is the problem you're trying to solve: why do you want an upstream set to master? Is it only because of rebase? We should probably get rebase.defaultUpstream = @{u}|origin|... -- To unsubscribe

Re: [PATCH] fetch: add new fetch.default configuration

2013-05-18 Thread Felipe Contreras
On Sat, May 18, 2013 at 1:43 PM, Ramkumar Ramachandra artag...@gmail.com wrote: Felipe Contreras felipe.contre...@gmail.com wrote: % git checkout --set-upstream-to master What is the problem you're trying to solve: why do you want an upstream set to master? I have explained that multiple

Re: [PATCH] fetch: add new fetch.default configuration

2013-05-18 Thread Eric Sunshine
On Fri, May 17, 2013 at 10:18 PM, Felipe Contreras felipe.contre...@gmail.com wrote: When the user has an upstream branch configured to track a remote tracking branch: % git checkout --set-upstream-to github/master Doing a 'git fetch' without any arguments would try to fetch 'github',