On Friday 2011-05-27 09:58, Lutz Jaenicke wrote: >> >> That's supposed to read 1.4.11 of course :) >> > >> >Hmm. For reasons I do not (yet?) understand I do not get the >> >tag with "git pull" and configure.ac stays at 1.4.10 in >> >"master". >> > >> >What am I doing wrong? >> >> That there is no tag, or even commit a potential tag could refer to. >> Someone must have forgotten push. > >Maybe. If I perform a "git clone" the tag is in the packed refs. >The tag itself (also see gitweb) includes the modification of config.ac >to reflect the bumped version number... `git remote update` only requests the branch heads, and since the v1.4.11 tag is not reachable through any branch (again - ugh), it does not get downloaded. `git fetch origin --tags` retrieves it, but of course that does not fix the underlying problem that a tag should be reachable[*] through a head. [*] Since ancient versions are out of focus, no heads are usually provided for these (e.g. v1.4.9.1); the fact that v1.4.9 is reachable is merely a sideeffect. -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
