From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx1.redhat.com ([209.132.183.28]) by merlin.infradead.org with esmtp (Exim 4.80.1 #2 (Red Hat Linux)) id 1WAh30-0001dd-65 for kexec@lists.infradead.org; Tue, 04 Feb 2014 14:32:23 +0000 Date: Tue, 4 Feb 2014 09:31:54 -0500 From: Vivek Goyal Subject: Re: More frequent kexec-tools releases Message-ID: <20140204143154.GA8373@redhat.com> References: <20140128184042.GA7098@redhat.com> <52E85B26.2080203@cn.fujitsu.com> <20140129142311.GA15077@redhat.com> <20140131052304.GC25099@verge.net.au> <20140131143047.GA10594@redhat.com> <20140204083151.GE30621@verge.net.au> <20140204124148.GH17028@verge.net.au> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20140204124148.GH17028@verge.net.au> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "kexec" Errors-To: kexec-bounces+dwmw2=twosheds.infradead.org@lists.infradead.org To: Simon Horman Cc: Dave Young , Zhang Yanfei , Kexec Mailing List , WANG Chao On Tue, Feb 04, 2014 at 09:41:48PM +0900, Simon Horman wrote: [..] > > > > Perhaps we could aim for every second kernel release and see how that goes? > > > > > > Sounds Good. Kernel releases are roughly 3 months apart. So that would > > > mean a kexec-tools release roughly around 6 months. This sounds like > > > a good start. > > > > > > So 3.13 was release recently. And last kexec-tools release was in march > > > 2013. May be it is a good idea to do one release now and then next one > > > can be after release of kernel 3.15, 3.17 and so on. > > > > Yes, I think so too. > > Would any of you object to me doing this with the current state of the > tree as of fe2c38cc0fc32573 ("Avoid buffer overflow on strncat usage"). I have no objection. Thanks Vivek _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec