This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Official GCC git repository
- From: Andreas Schwab <schwab at suse dot de>
- To: Rafael Espindola <espindola at google dot com>
- Cc: Daniel Berlin <dberlin at dberlin dot org>, Ludovic Courtès <ludo at gnu dot org>, gcc at gcc dot gnu dot org
- Date: Mon, 22 Dec 2008 11:34:42 +0100
- 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> <38a0d8450812210343y7da777ej3c986954195d5a56@mail.gmail.com>
Rafael Espindola <espindola@google.com> writes:
>>> 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.
As I wrote in a followup, this is not really a good idea. You should
put the other remote heads under a different directory, perhaps like
this:
$ git config --add remote.origin.fetch '+refs/remotes/*:refs/remotes/gcc/*'
This tells git to fetch the remote heads matching refs/remotes/* and to
make them availble locally under refs/remotes/gcc.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."