-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Roland McGrath wrote: >> Thanks for the reminder to manually update the version number. At first >> I forgot. Would it be an idea to up the version number directly after a >> release in git, so users that test against the elfutils git tree get the >> _ELFUTILS_PREREQ behavior that will be in effect with the next release? > > I wouldn't mind that if Uli thinks it's OK.
For this the definition of _ELFUTILS_PREREQ would have to be changed to include a sub-minor version number. Right after the release the tree certainly cannot be tagged with the version number of the next release. In glibc I tag the tree with 2.x.90 after the release of 2.x. - -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAknoslsACgkQ2ijCOnn/RHSo1QCcDW6r91Kxy3SeWR+xyQZFn6pu Im0AmgLyLs48dhCzNY9dRWYKB2eeJn8E =PMk4 -----END PGP SIGNATURE----- _______________________________________________ elfutils-devel mailing list [email protected] https://fedorahosted.org/mailman/listinfo/elfutils-devel
