Am 04.08.2014 18:27, schrieb Greg KH:
On Mon, Aug 04, 2014 at 07:45:55AM +0200, Alexander Holler wrote:
Hello,
Some time ago (a year or two ;) ), I've already mentioned that the tag
import for newly created linux-3.x.y branches was missed.
This still happens often (e.g. the tag for 3.15 entered stable some days
later) and now I see again linux-3.16.y without a 3.16 tag.
And if you waited a few more hours, you would have seen it show up.
That was due to an issue on my end (not near my 2-factor auth key), so I
couldn't push the tag.
The result is that in Linux kernel git repositories which only have stable
as origin linux-3.16.y currently describes itself as:
v3.16-rc7-115-g19583ca
which doesn't look like a suggested stable kernel.
Don't rely on the linux-stable kernel repo to always have an updated
version of Linus's tree in it, that is _not_ it's goal or requirement.
I'll update it when I remember, and yes, sometimes I forget to push the
tags.
It's not a big deal, just use Linus's tree if you want the latest
version of his tree, don't rely on my to keep it in sync for you, you
could do it all on your own on your end if you really wanted it.
I use Linus tree or one of the various next if I want the latest
bleeding edge patches. But I use the stable tree to follow the latest
stable to get security fixes for machines where I only use and where I'm
only interested in the stable tree.
So what happens here is that I fetch the trees on my workstation which
has Linus tree and stable and some other remote branches, I see a new
main version, and when I want to start my update procedere (fetch the
latest stable and rebase my own ignored, refused or not submitted
patches) on boxes which only have the stable as remote, they end up with
a version like above (because of the missing main version tag).
I really suggest to use a script to create new linux-3.x.y branches and add
the necessary tag(s) to it, even if the script would just contain 2 lines.
;)
I can't 'add' a tag, I must pull and push Linus's tags, and no, I don't
use a script for all of that, it's not needed, and in this case, it
wouldn't have helped anything anyway.
I wouldn't have written this mail if it would have happened at least
twice in row (3.15 and 3.16).
And I'm not sure what's the big deal to write a mini-script which
creates a branch and pushes or pulls the tag in one step.
Ok, I've no idea about your workflow (and your 2 factor identification),
but I assume you only create a new branch for a main version if Linus
has already created and thus published a new main version (and tag). And
this happens rarely which might be the reason that this problem happens
that often because some manually done steps might be easily forgotten
(nobody is perfect).
It isn't such that write a mail every time when this happens, and the
last time I've written a mail is now really long time ago.
But I promise to not send such an reminder again.
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