This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Official GCC git repository
- From: Rafael Espindola <espindola at google dot com>
- To: Andreas Schwab <schwab at suse dot de>
- Cc: Daniel Berlin <dberlin at dberlin dot org>, Ludovic CourtÃs <ludo at gnu dot org>, gcc at gcc dot gnu dot org
- Date: Sun, 21 Dec 2008 11:43:59 +0000
- Subject: Re: Official GCC git repository
- References: <47D7F8DA.8060703@codewiz.org> <20080314144142.GC17210@redhat.com> <20080326163011.GA20021@redhat.com> <4aca3dc20803261138s20fb11famceefc20905543ef@mail.gmail.com> <20080415024917.GA20204@localhost.localdomain> <4aca3dc20804142207s2c050191s3db1ddcf40621b9e@mail.gmail.com> <87bq4bl14v.fsf@gnu.org> <87y77ffeeu.fsf@gnu.org> <4aca3dc20804150942k4e48b540i61653bed10738b69@mail.gmail.com> <jemynvvy8n.fsf@sykes.suse.de>
>> git config --add remote.origin.fetch '+refs/remotes/*:refs/remotes/*'
>
> This will put the remote branch heads in refs/remotes, you might want to
> put them in refs/remotes/origin instead.
>
> $ git config --add remote.origin.fetch '+refs/remotes/*:refs/remotes/origin/*'
One small problem I have with this. When I do "git branch lto
origin/lto" the generated config entry says:
[branch "lto"]
remote = origin
merge = refs/heads/lto
and "git pull" will fail. Manually updating it to
[branch "lto"]
remote = origin
merge = refs/remotes/lto
solves the problem
>
> Andreas.
>
Cheers,
--
Rafael Avila de Espindola
Google | Gordon House | Barrow Street | Dublin 4 | Ireland
Registered in Dublin, Ireland | Registration Number: 368047