Le 20/10/2016 à 11:20, Paul Jakma a écrit : > On Thu, 20 Oct 2016, Nicolas Dichtel wrote: > >> A naive question: is it expected that the tag of the release is not on a >> branch? > > A point-release of an old release maybe could just be referenced by the tag I > guess - not really expecting more work there. Anyone feel strongly about it > needing a branch reference, duplicating the tag? what are the practical > consequences of just a tag - it still appears in gitk and the web git viewer > right? For example, a clone of the repo does not fetch by default this kind of tag. You need to do 'git fetch -t'.
> > The commit the 1.1.0 tag is pointing at should definitely be a commit on the > master branch. That's a mistake. :) Ok :) > >> $ git log quagga-1.1.0 >> 258f3dad6471 (tag: quagga-1.1.0) release: Bump version to 1.1.0 >> de58bdb9cdbd build: remove werror from buildtest.sh for now >> cfb1fae25f8c (HEAD -> master) zebra: stack overrun in IPv6 RA receive code >> (CVE-2016-1245) >> >> The last two commits are "flooting" commits. >> >> $ git branch --contains quagga-1.1.0 >> => nothing > > I shall fix that after I have fetched a cup of tea... Thank you, Nicolas _______________________________________________ Quagga-dev mailing list Quagga-dev@lists.quagga.net https://lists.quagga.net/mailman/listinfo/quagga-dev
