Re: Creating new remote branch in git?

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Smith <greg(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Creating new remote branch in git?
Date: 2011-06-14 02:54:37
Message-ID: 201106140254.p5E2sbY18872@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera wrote:
> Excerpts from Bruce Momjian's message of lun jun 13 18:38:46 -0400 2011:
> > Andrew Dunstan wrote:
>
> > > Is putting remotes in your ~/.gitconfig good practice? I certainly
> > > don't have any in mine.
> >
> > Putting 'github' in there allows me to push/pull from github branches
> > without having to specify the github URL.
>
> I think his point is that they are more properly specified in each
> repo's .git/config file, not the global $HOME/.gitconfig. If you were
> to check out some other, unrelated project, you could end up pushing
> unrelated branches to PG's repo ... Not sure if this is really
> possible, but it certainly seems scary to do things that way.

I understand now --- that it is risky to create an "origin" branch in
~/.gitconfig. I am now using an alias:

[alias]
pgclone = clone ssh://git(at)gitmaster(dot)postgresql(dot)org/postgresql.git

I assume the 'github' branch in ~/.gitconfig is fine.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2011-06-14 04:09:49 Re: pgbench cpu overhead (was Re: lazy vxid locks, v1)
Previous Message Bruce Momjian 2011-06-14 02:11:16 Re: pg_trgm: unicode string not working