From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 37EEEC433EF for ; Fri, 1 Apr 2022 05:32:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242933AbiDAFea (ORCPT ); Fri, 1 Apr 2022 01:34:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44458 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239652AbiDAFe3 (ORCPT ); Fri, 1 Apr 2022 01:34:29 -0400 Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B38EB19B07F for ; Thu, 31 Mar 2022 22:32:40 -0700 (PDT) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id CAC025C010C; Fri, 1 Apr 2022 01:32:36 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Fri, 01 Apr 2022 01:32:36 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h=cc :cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; bh=tcUHCZ53Jdbxt3XM3m9APQ4wP6taL9tWKdFazA nsE1Q=; b=Lue6a5fIOhtXTvibHIoKWvyT6sMWrVpliC95XrdDAeppnfZ82pRiHU AU5/kB9TVENGQabsg+JJVD7Op5gq17upMEkP4STGcgbHbGccqp8DBi5xj6neK6YQ qhuk1XmJpzGZg2C6VCm8kN9CBoXUyBUtsCxi7z4ek5qiAgVNNePG9ptJ9V4/dxoK DsqtDmiEvOYs4sl6Rk5iLquB/U7HsJ3Q9oCuNfHHk3RiUVs5GlpVQ3cnLEqAqjCx j/jak3A1AuVOVrzmx3MianLsLISxPgJpYyxyeMbb4NDyeCYhE1Lr95KMjH3F3RYZ RQX+SOH2xK760EAGUqveBJYSbuGSiHGA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=tcUHCZ53Jdbxt3XM3 m9APQ4wP6taL9tWKdFazAnsE1Q=; b=d1OQ0D7XlkBmMglXdGmsdBW0pKb+/QJX0 pfMYhJqNDAzzxkCswKkOWbyWc04rr5D9sVYljH6GSdfCALbtS2B7m/Q7iBXiFroW dT7Bz6XGNJOkY8ErSDsEnud15flCghu82Rgn9m/GxlLaFSSLk5kVdUvcMjNMoRXA 9uTtSh4PAKnywvUW3UsY3pDSIcI28qSsJI0OL6sJQBNHDsYlXrmmJND9McGZH4QV AP9Tx46QpC0fhd5Ettx8dVg/vTGc0/y+VnjfnvfLaRvOqa5DCRdpkFNn9cknwsU9 UMcsvSFHSbKMIzgg5Z5dPrr+w/TLilnQJ/rMPSD8pULXbydticJCg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudeihedgleeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjsehttdertddttddvnecuhfhrohhmpefirhgvghcu mffjuceoghhrvghgsehkrhhorghhrdgtohhmqeenucggtffrrghtthgvrhhnpeevueehje fgfffgiedvudekvdektdelleelgefhleejieeugeegveeuuddukedvteenucevlhhushht vghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehgrhgvgheskhhrohgrhh drtghomh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 1 Apr 2022 01:32:36 -0400 (EDT) Date: Fri, 1 Apr 2022 07:32:34 +0200 From: Greg KH To: Vitaly Chikunov Cc: Sasha Levin , stable@vger.kernel.org Subject: Re: Why rolling trees aren't updated last week? Message-ID: References: <20220401025038.d4hpgzpl6jnxkyyw@altlinux.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220401025038.d4hpgzpl6jnxkyyw@altlinux.org> Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Fri, Apr 01, 2022 at 05:50:38AM +0300, Vitaly Chikunov wrote: > Hello, > > Why linux-rolling-lts and linux-rolling-stable trees aren't updated last > week and stay on the previous lts and stable releases? We forgot, I'll go update them in a bit, thanks. greg k-h