Robert Haas wrote: > On Mon, Jun 13, 2011 at 10:54 PM, Bruce Momjian <br...@momjian.us> wrote: > > 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://g...@gitmaster.postgresql.org/postgresql.git > > > > I assume the 'github' branch in ~/.gitconfig is fine. > > That, too, would better off inside $REPO/.git/config, although it's > certainly less risky than the other one. It doesn't make much sense > to have an upstream that applies across every repository you have > checked out.
Wouldn't I conceivably use github with a variety of projects? I try to use ~/.gitconfig so I don't have to redo a lot of stuff when I reinstall my PG git tree. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
