Magnus Hagander wrote: > >> > 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. > > Yes, but your reference goes to a specific repository at github > (bmomjian/postgres). Which wouldn't be correct for any other > project...
Ah, I see your point. Thanks. I renamed it 'pggithub'. I think I need to read Pro Git (http://progit.org/book/), though I am not sure that would have helped me in this exact case. -- 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
