From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Aidan Van Dyk <aidan(at)highrise(dot)ca>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: So git pull is shorthand for what exactly? |
Date: | 2010-10-01 17:08:45 |
Message-ID: | 4CA6159D.9070300@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10/01/2010 12:49 PM, Tom Lane wrote:
> Magnus Hagander<magnus(at)hagander(dot)net> writes:
>> On Fri, Oct 1, 2010 at 17:53, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2010-10-01 17:14:48 | Re: So git pull is shorthand for what exactly? |
Previous Message | Tom Lane | 2010-10-01 16:49:54 | Re: So git pull is shorthand for what exactly? |