Daniel Barkalow <barkalow@xxxxxxxxxxxx> writes:
> Is this actually supported in config files? At least for pulls, the "tag
> <tag>" notation is only available on the command line, afaict.
That is the only difference as far as I remember. But you are
right in that the set of refspecs allowed on the command line
does not have to coincide with the ones in remotes file or the
config (the latter two should match, though), and the latter may
not be documented (the intention was to match all of them so the
quoted documentation was enough, but having "tag <tag>" in
config does not make sense). Documentation/config.txt could use
a bit of updates. Hint, hint.
> I think that having "<ref>:" or "<ref>" in a config file fetch
> line would be really bad; these refs would always be merged into any
> current head (without any remote tracking) when the remote is fetched
> from?
It's not bad at all. Why people are so eager to _force_
tracking on other people, I do not understand.
I had a moral equivalent of this in .git/remotes/origin (back
then .git/config did not exist) when I was a contributor:
[remote "origin"]
url = git.kernel.org:/pub/scm/git/git.git/
fetch = refs/heads/master
If the user does not want to track, he does not have to.
-
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