On 02/05/2011 02:18 AM, Johan Herland wrote:
Today, when you fetch from a remote, the config typically says
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = ...
But this fetch refspec does not tell the full story. In addition to mapping
origin's refs/heads/* into refs/remotes/origin/*, it also fetches origin's
HEAD into refs/remotes/origin/HEAD, and anything in origin's refs/tags/*
that happen to point to a fetched object is fetched into refs/tags/* (aka.
auto-following tags). These other fetches are not explicitly specified in
the config, but "magically" happen anyway. Instead of having such implicit
refspecs, I'd rather have all fetch refspecs listed explicitly in the
config, like this (for replicating current layout):
[remote "origin"]
fetch = +HEAD:refs/remotes/origin/HEAD
fetch = +refs/heads/*:refs/remotes/origin/*
fetch = ~refs/tags/*:refs/tags/*
url = ...
or this (in the proposed new layout):
[remote "origin"]
fetch = +HEAD:refs/remotes/origin/HEAD
fetch = +refs/heads/*:refs/remotes/origin/heads*
fetch = +refs/tags/*:refs/remotes/origin/tags/*
url = ...
I would appreciate this as well; the less implicit behavior in areas
like this, the better :-)
--
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
skype: kpfleming | jabber: kfleming@xxxxxxxxxx
Check us out at www.digium.com & www.asterisk.org
--
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