| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| 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 01:54:38 |
| Message-ID: | 1308016383-sup-1480@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2011-06-14 01:56:13 | Re: pgbench cpu overhead (was Re: lazy vxid locks, v1) |
| Previous Message | Shigeru Hanada | 2011-06-14 01:51:25 | Re: FOREIGN TABLE doc fix |