From: Samuel Tardieu <sam@rfc1149.net>
To: git@vger.kernel.org
Subject: Remotes order in "git remote update"
Date: Sun, 09 Mar 2008 11:22:33 +0100 [thread overview]
Message-ID: <2008-03-09-11-22-34+trackit+sam@rfc1149.net> (raw)
It looks like remote repositories are ordered alphabetically by their
local names when doing a "git remote update". In a project I follow,
it has an unfortunate consequence: a dumb remote repository using
"http://" is fetched first, while many commits are shared between all
the upstreams I follow.
If remotes were fetched using their order in .git/config, it would
fetch from a "git://" remote repository first, limiting transfers from
the dumb remote repository. Is there a way to force the update order
short of changing the local names or issuing multiple fetch commands?
Sam
--
Samuel Tardieu -- sam@rfc1149.net -- http://www.rfc1149.net/
next reply other threads:[~2008-03-09 10:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-09 10:22 Samuel Tardieu [this message]
2008-03-09 10:38 ` Remotes order in "git remote update" Junio C Hamano
2008-03-09 11:21 ` Samuel Tardieu
2008-03-09 20:50 ` Johannes Schindelin
2008-03-10 5:50 ` Junio C Hamano
2008-03-10 11:11 ` Johannes Schindelin
2008-03-10 8:17 ` Samuel Tardieu
2008-03-10 11:13 ` Johannes Schindelin
2008-03-10 19:21 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2008-03-09-11-22-34+trackit+sam@rfc1149.net \
--to=sam@rfc1149.net \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).