Re: Remotes order in "git remote update"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On  9/03, Johannes Schindelin wrote:

| 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...

I could do that, but it means that if I add a new remote, it won't enter
the default group by itself since I defined it explicitely. I think
respecting the order given in the .git/config file when not using a
group doesn't hurt and may help.

Or maybe we should add a remotes.reference configuration variable which
lists the remote to use first if it belongs to the list of remotes we
are going to fetch from. Or at least, make origin the first fetched
remote, but I know some projects where origin uses a dumb protocol while
other contributors have up-to-date non-dumb public repositories.

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux