Bug 247249
Summary: | xen doesn't show changeset information | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Gerd Hoffmann <kraxel> | ||||||
Component: | kernel-xen | Assignee: | Gerd Hoffmann <kraxel> | ||||||
Status: | CLOSED NOTABUG | QA Contact: | Martin Jenner <mjenner> | ||||||
Severity: | low | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 5.0 | CC: | riel, xen-maint | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2007-10-25 13:48:06 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Gerd Hoffmann
2007-07-06 11:27:41 UTC
Created attachment 158651 [details]
xen src tree patch
Created attachment 158652 [details]
kernel spec file patch
posted for review on 2007-07-22 I think we need this to include a clear indication that the release is NOT a specific upstream changeset, but is in fact our own variant on that, complete with other patches. So perhaps xen_changeset : 15042.el5 makes sense. Requesting for 5.2. Also, what do we do about the fact that userland is based off multiple different releases (one for python, another for hvm environment); and that the kernel and hypervisor are based off different csets, too? Sounds like "unavailable" is actually the most accurate response to a user asking what our Xen version is. :) Personally I recommend against including any form of changeset information, simply because there is no meaningful changeset we can provide. The HV may be based off 3.1, but its got a number of patches added. The userspace bears no resemblance to any upstream changeset. Nor does the kernel. We should not try to pretend that we have any correspondance to a changeset because it'll just encourage people to make meaningless comparisons between functionality/bugs in upstream vs our tree. change QA contact |