Bug 592478 - RHEL5->RHEL6 patch list check (yhalperi@redhat.com)
Summary: RHEL5->RHEL6 patch list check (yhalperi@redhat.com)
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm   
(Show other bugs)
Version: 6.0
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Yonit Halperin
QA Contact: Virtualization Bugs
Keywords: Tracking
Depends On:
Blocks: Rhel5KvmTier2 580953 KvmRhel5to6Patches
TreeView+ depends on / blocked
Reported: 2010-05-14 21:43 UTC by Eduardo Habkost
Modified: 2014-01-20 23:59 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-07-05 11:00:29 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Eduardo Habkost 2010-05-14 21:43:01 UTC
This bug is for the task of checking for RHEL5 KVM patches that are not yet upstream or not included on RHEL6

Comment 2 Eduardo Habkost 2010-05-14 21:55:56 UTC
Sorry for the Bugzilla spam on virt-maint. Removing virt-maint from CC/assignee.

Comment 4 RHEL Product and Program Management 2010-06-07 15:56:26 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for

Comment 6 Yonit Halperin 2010-06-15 05:54:24 UTC
updated status

Comment 10 Lawrence Lim 2010-07-02 04:53:07 UTC
What are we suppose to do with this bug? If its merely a tracker, all flag should be removed.

Comment 11 Eduardo Habkost 2010-07-05 11:00:29 UTC
(In reply to comment #10)
> What are we suppose to do with this bug? If its merely a tracker, all flag
> should be removed.    

If the section under your name has all patches already reviewed, the bug can be closed.

Note You need to log in before you can comment on or make changes to this bug.