From: Simon Horman <horms@verge.net.au>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Kexec Mailing List <kexec@lists.infradead.org>,
Dave Young <dyoung@redhat.com>,
Zhang Yanfei <zhangyanfei@cn.fujitsu.com>,
WANG Chao <chaowang@redhat.com>
Subject: Re: More frequent kexec-tools releases
Date: Thu, 6 Feb 2014 10:55:13 +0900 [thread overview]
Message-ID: <20140206015513.GX5125@verge.net.au> (raw)
In-Reply-To: <20140205132015.GA6042@redhat.com>
On Wed, Feb 05, 2014 at 08:20:15AM -0500, Vivek Goyal wrote:
> On Wed, Feb 05, 2014 at 03:49:06PM +0900, Simon Horman wrote:
> > On Wed, Feb 05, 2014 at 09:12:26AM +0800, Zhang Yanfei wrote:
> > > On 02/04/2014 08:41 PM, Simon Horman wrote:
> > > > On Tue, Feb 04, 2014 at 05:31:51PM +0900, Simon Horman wrote:
> > > >> On Fri, Jan 31, 2014 at 09:30:47AM -0500, Vivek Goyal wrote:
> > > >>> On Fri, Jan 31, 2014 at 02:23:04PM +0900, Simon Horman wrote:
> > > >>>
> > > >>> [..]
> > > >>>>> Simon what do you think? A kexec-tools release every 4 months or every
> > > >>>>> 6 months. Does it make sense to you?
> > > >>>>
> > > >>>> 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").
> > > >
> > >
> > > NO objection.
> >
> > Done :)
>
> Thanks Simon. I did git pull but I don't see new tag in my tree. Not sure
> why.
Could you try again? I messed up the push.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2014-02-06 1:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 18:40 More frequent kexec-tools releases Vivek Goyal
2014-01-29 1:36 ` Zhang Yanfei
2014-01-29 14:23 ` Vivek Goyal
2014-01-31 5:23 ` Simon Horman
2014-01-31 14:30 ` Vivek Goyal
2014-02-04 8:31 ` Simon Horman
2014-02-04 12:41 ` Simon Horman
2014-02-04 14:31 ` Vivek Goyal
2014-02-05 1:12 ` Zhang Yanfei
2014-02-05 6:49 ` Simon Horman
2014-02-05 13:20 ` Vivek Goyal
2014-02-06 1:55 ` Simon Horman [this message]
2014-02-06 14:23 ` Vivek Goyal
2014-02-06 23:58 ` Simon Horman
2014-02-07 2:20 ` Dave Young
2014-02-07 14:34 ` Vivek Goyal
2014-02-12 1:16 ` Simon Horman
2014-02-25 4:12 ` WANG Chao
2014-01-29 16:46 ` Khalid Aziz
2014-01-29 16:52 ` Vivek Goyal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140206015513.GX5125@verge.net.au \
--to=horms@verge.net.au \
--cc=chaowang@redhat.com \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=vgoyal@redhat.com \
--cc=zhangyanfei@cn.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox