On 8/22/2014 4:11 AM, Daniel P. Berrange wrote:
On Thu, Aug 21, 2014 at 09:02:17AM -0700, Armando M. wrote:
Hi folks,
According to [1], we have ways to introduce external references to commit
messages.
These are useful to mark certain patches and their relevance in the context
of
On 8/21/2014 11:55 AM, Sean Dague wrote:
On 08/21/2014 11:02 AM, Armando M. wrote:
Hi folks,
According to [1], we have ways to introduce external references to
commit messages.
These are useful to mark certain patches and their relevance in the
context of documentation, upgrades, etc.
I
On Fri, Aug 22, 2014 at 2:11 AM, Daniel P. Berrange berra...@redhat.com
wrote:
On Thu, Aug 21, 2014 at 09:02:17AM -0700, Armando M. wrote:
Hi folks,
According to [1], we have ways to introduce external references to commit
messages.
These are useful to mark certain patches and their
On Thu, Aug 21, 2014 at 09:02:17AM -0700, Armando M. wrote:
Hi folks,
According to [1], we have ways to introduce external references to commit
messages.
These are useful to mark certain patches and their relevance in the context
of documentation, upgrades, etc.
I was wondering if it
Hi folks,
According to [1], we have ways to introduce external references to commit
messages.
These are useful to mark certain patches and their relevance in the context
of documentation, upgrades, etc.
I was wondering if it would be useful considering the addition of another
tag:
On 08/21/2014 11:02 AM, Armando M. wrote:
Hi folks,
According to [1], we have ways to introduce external references to
commit messages.
These are useful to mark certain patches and their relevance in the
context of documentation, upgrades, etc.
I was wondering if it would be useful
A concern with this approach is it's pretty arbitrary, and not always
clear which bugs are being addressed and how severe they are.
Well, establishing whether LP reports are actual bugs and assigning the
severity isn't what triaging is for?
An idea that came up in the Infra/QA meetup was