Re: Creating new remote branch in git? - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Creating new remote branch in git?
Date
Msg-id 4DF66E32.7040905@dunslane.net
Whole thread Raw
In response to Re: Creating new remote branch in git?  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Creating new remote branch in git?
List pgsql-hackers

On 06/13/2011 02:26 PM, Bruce Momjian wrote:
> I found the cause. When I added 'github' to ~/.gitconfig a few months
> ago, I copied this line from .git/config:
>
>     fetch = +refs/heads/*:refs/remotes/origin/*
>
> If this line is in ~/.gitconfig for both 'origin' and 'github', git
> cannot create .git/config entries.
>
> Attached is my corrected  ~/.gitconfig file.  I now use only the 'url'
> branch entries, which is all that is needed.
>
[...]
> [remote "origin"]
>     url = ssh://git@gitmaster.postgresql.org/postgresql.git
> # Do not add the next line or .git/config is not updated.
> #    fetch = +refs/heads/*:refs/remotes/origin/*
> [remote "github"]
>     url = git@github.com:bmomjian/postgres.git


Is putting remotes in your ~/.gitconfig  good practice? I certainly 
don't have any in mine.

The one for "origin" seems a particularly bad idea to me, although I 
don't claim that my git-fu is of the highest.


>     pager = "less -x4 -E"

I experimented with this setting quite a bit before getting it the way I 
wanted. You might find this works better:
   pager = less -+$LESS -FRSX


cheers

andrew





pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: Make relation_openrv atomic wrt DDL
Next
From: Tom Lane
Date:
Subject: Re: ECPG parse.pl and parse2.pl