Re: So git pull is shorthand for what exactly?
От | Andrew Dunstan |
---|---|
Тема | Re: So git pull is shorthand for what exactly? |
Дата | |
Msg-id | 4CA6159D.9070300@dunslane.net обсуждение исходный текст |
Ответ на | Re: So git pull is shorthand for what exactly? (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: So git pull is shorthand for what exactly?
Re: So git pull is shorthand for what exactly? |
Список | pgsql-hackers |
On 10/01/2010 12:49 PM, Tom Lane wrote: > Magnus Hagander<magnus@hagander.net> writes: >> On Fri, Oct 1, 2010 at 17:53, Tom Lane<tgl@sss.pgh.pa.us> wrote: >>> BTW, I've noticed that "git push" will reject an attempt to push an >>> update in one branch if my other branches are not up to date, even >>> if I am not trying to push anything for those branches. That's >>> pretty annoying too; is there a way around that? >> I admit I haven't tried it, but won't that get fixed if you push just >> the current branch? E.g. "git push origin master"? > I'll try that next time; I haven't gotten further than using git push's > default behavior. "git push origin HEAD" pushes the current branch, whatever it might be. That might be a useful alias for you to set up. cheers andrew
В списке pgsql-hackers по дате отправления: