Re: So git pull is shorthand for what exactly?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: 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 16:49:54
Message-ID: 20817.1285951794@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2010-10-01 17:08:45 Re: So git pull is shorthand for what exactly?
Previous Message Heikki Linnakangas 2010-10-01 16:48:25 Re: So git pull is shorthand for what exactly?