Re: So git pull is shorthand for what exactly?

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Aidan Van Dyk <aidan(at)highrise(dot)ca>
Subject: Re: So git pull is shorthand for what exactly?
Date: 2010-10-01 18:28:11
Message-ID: 4CA6283B.1010107@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10/01/2010 01:23 PM, Andres Freund wrote:
>
> If you want that as a default behaviour:
> "For example, to default to pushing only the current branch to origin use git
> config remote.origin.push HEAD. Any valid<refspec> (like the ones in the
> examples below) can be configured as the default for git push origin."

It's just occurred to me that this might be a slightly dangerous
setting. If HEAD happens to be your private topic branch because you
forgot to switch back to the main branch, it will cheerfully push your
no longer private branch. If you have separate git dirs for each live
branch, it might be better to set the default push refspec to that
branch explicitly. Of course, if you're using the multiple workdir
pattern, that won't work because then they all share a common .git/config.

But maybe I'm just being a bit paranoid.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2010-10-01 18:34:46 Re: patch: tsearch - some memory diet
Previous Message Robert Haas 2010-10-01 18:23:57 Re: patch: tsearch - some memory diet