Messages in this thread | | | From | Sven Joachim <> | Subject | Re: [ANNOUNCE] The longterm Linux 2.6.35.14 kernel is released | Date | Tue, 02 Aug 2011 20:39:16 +0200 |
| |
On 2011-08-02 20:17 +0200, Andi Kleen wrote:
> On Tue, Aug 02, 2011 at 09:05:48AM +0200, Sven Joachim wrote: >> On 2011-08-01 23:59 +0200, Andi Kleen wrote: >> >> > The longterm Linux kernel 2.6.35.14 is released. >> > >> > A note on the 2.6.35.13 git tags & branches: when releasing 2.6.35.13 I made >> > a mistake which resulted in the v2.6.35.13 tag being on a different >> > branch than the master tree. I decided the continue on the branch, >> > not the tag, so you have to delete the v2.6.35.13 tag -- if you're >> > using that -- and refetch the new tag. If you just use the "master" branch >> > or the released patches/tarballs you don't need to do anything. Sorry about that. >> >> Well, there is still a little problem with the git repository. You have >> pushed the tag but not the master branch to git.kernel.org. > > I checked the tree on master, it is uptodate. Don't know why it's > not reaching the main git server. Maybe have to wait a bit longer.
I don't think that's the problem, since the v2.6.35.14 tag and the commits that lead to it have been at git.kernel.org/pub/scm/linux/kernel/git/longterm/linux-2.6.35.y.git for at least twelve hours. The problem is that while the tag is there, the master branch is still at v2.6.35.13-original. This happens if you just "git push v2.6.35.14" without _also_ explicitly pushing the master branch. In that case, the commits leading to v2.6.35.14 get pushed (and can be fetched with "git fetch -t") but are not on any branch.
Linus himself had already made this mistake at least twice, so it can happen to anyone, I guess. :-)
Cheers, Sven
| |