| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | 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 17:23:40 |
| Message-ID: | 201010011923.41715.andres@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Friday 01 October 2010 18:48:25 Heikki Linnakangas wrote:
> On 01.10.2010 18:53, Tom Lane 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?
>
> Yeah, that's annoying. You can do "git push origin <branch>", and it
> will only try to push that branch, ignoring the others.
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."
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2010-10-01 17:37:03 | Re: wip: functions median and percentile |
| Previous Message | Andrew Dunstan | 2010-10-01 17:21:38 | Re: So git pull is shorthand for what exactly? |