Just to make a long story short, all I would like is that a new stable
branch in the stable tree only appears iff the stable tree already
contains the accompanying tag.
Otherwise a lot of confusion at the user side might happen because a
stable kernel identifies itself as
v3.16-rc7-115-g19583ca
when using git describe and even with
3.16.0-foo-115-g19583ca
as the kernel version (e.g. in uname if CONFIG_LOCALVERSION=-foo is used).
But both are 3.16.0 without any additional patches.
And I assume most human brains are build such that they don't identify
kernel versions using the commit number but the nice "human readable"
stuff before it, about which I'm pretty happy that it exists and whose
"inventor" should receive kudos all the time. ;)
I hope that explanation doesn't leave any open questions why I thought
another reminder (after one or two years when I send such the last time)
might make sense and wouldn't be handled as an offense.
Alexander Holler
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html