Re: So git pull is shorthand for what exactly?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 18:04:25
Message-ID: AANLkTikL-nVbUPJEmKDKXAHx5sfz6+j8zCjPsFPhsH4B@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 1, 2010 at 11:53 AM, 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?

Are you sure? For me, the pushes on the up-to-date branches succeed
and only the out-of-date ones fail.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-10-01 18:06:17 Re: Patch author name on commitfest page
Previous Message Marios Vodas 2010-10-01 18:02:02 timestamp_in DirectFunctionCall