From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Schindelin Subject: Re: Remotes order in "git remote update" Date: Sun, 9 Mar 2008 21:50:04 +0100 (CET) Message-ID: References: <2008-03-09-11-22-34+trackit+sam@rfc1149.net> <7vbq5op4gt.fsf@gitster.siamese.dyndns.org> <2008-03-09-12-21-35+trackit+sam@rfc1149.net> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Junio C Hamano , git@vger.kernel.org To: Samuel Tardieu X-From: git-owner@vger.kernel.org Sun Mar 09 21:51:25 2008 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1JYSUE-0004Zq-EF for gcvg-git-2@gmane.org; Sun, 09 Mar 2008 21:51:14 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753922AbYCIUuF (ORCPT ); Sun, 9 Mar 2008 16:50:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753881AbYCIUuE (ORCPT ); Sun, 9 Mar 2008 16:50:04 -0400 Received: from mail.gmx.net ([213.165.64.20]:49499 "HELO mail.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1753799AbYCIUuC (ORCPT ); Sun, 9 Mar 2008 16:50:02 -0400 Received: (qmail invoked by alias); 09 Mar 2008 20:50:00 -0000 Received: from host86-138-198-40.range86-138.btcentralplus.com (EHLO [192.168.1.89]) [86.138.198.40] by mail.gmx.net (mp045) with SMTP; 09 Mar 2008 21:50:00 +0100 X-Authenticated: #1490710 X-Provags-ID: V01U2FsdGVkX1+b6Pl8tw2bLLqP2WvspqQNn8WsYjKpk/pyAcQ5pB RJiZ+rsxLRHjP+ X-X-Sender: gene099@racer.site In-Reply-To: <2008-03-09-12-21-35+trackit+sam@rfc1149.net> User-Agent: Alpine 1.00 (LSU 882 2007-12-20) X-Y-GMX-Trusted: 0 Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Hi, On Sun, 9 Mar 2008, Samuel Tardieu wrote: > On 9/03, Junio C Hamano wrote: > > | Samuel Tardieu writes: > | > | > It looks like remote repositories are ordered alphabetically by their > | > local names when doing a "git remote update". > | > | I think the reimplementaiton in 'next' that will hopefully be in 1.5.5 > | will keep the list of remotes in the order read from the config. > > Indeed it does, thanks. Well, technically this is a regression. If you really want to order your remotes, why not add something like [remotes] default = my-first-remote my-second-remote [...] to the config? That is what the (recently fixed in builtin-remote) remote groups are for... Ciao, Dscho