From: Agostino Sarubbo <ago@gentoo.org>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: security bugs and release
Date: Wed, 26 Jun 2013 01:56:15 +0200 [thread overview]
Message-ID: <57196337.66J9t5sj8U@devil> (raw)
In-Reply-To: <51CA2342.3020902@citrix.com>
On Wednesday 26 June 2013 00:09:54 Andrew Cooper wrote:
> I would be interested if you could provide examples of upstream projects
> which do issues brand new releases for every security fix
Tbh, very few project do the same of you, and I usually see the new release in
few time...
Anyway you didn't answer to my question.
> If there is any confusion regarding patches and versions, please refer
> to http://wiki.xen.org/wiki/Security_Announcements which provides all
> details (although I note it is out of date with respect to XSA-57).
You didn't understand the point.
--
Agostino Sarubbo
Gentoo Linux Developer
next prev parent reply other threads:[~2013-06-25 23:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 17:07 security bugs and release Agostino Sarubbo
2013-06-25 23:09 ` Andrew Cooper
2013-06-25 23:56 ` Agostino Sarubbo [this message]
2013-06-26 9:21 ` Ian Campbell
2013-06-26 13:54 ` Pasi Kärkkäinen
2013-06-26 15:21 ` Agostino Sarubbo
2013-06-26 15:24 ` Agostino Sarubbo
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=57196337.66J9t5sj8U@devil \
--to=ago@gentoo.org \
--cc=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xen.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.