Bug 460137 - RHEL4: Implement rh-configs-prep
Summary: RHEL4: Implement rh-configs-prep
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.8
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Prarit Bhargava
QA Contact: Martin Jenner
URL:
Whiteboard:
Depends On:
Blocks: 461304
TreeView+ depends on / blocked
 
Reported: 2008-08-26 13:04 UTC by Prarit Bhargava
Modified: 2012-06-20 16:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 16:17:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Initial patch (1.86 KB, patch)
2008-08-26 13:04 UTC, Prarit Bhargava
no flags Details | Diff
patch v2 (1.85 KB, patch)
2008-08-26 13:07 UTC, Prarit Bhargava
no flags Details | Diff

Description Prarit Bhargava 2008-08-26 13:04:41 UTC
Created attachment 314993 [details]
Initial patch

RHEL5 has a make option, rh-configs-prep, which populates the top level configs directory with .configs that have had nonint_config run on them.

Port this code into RHEL4.

This may require additional (or future?) kernel.spec file changes -- however, this BZ is to get the initial change into redhat/Makefile and redhat/configs/Makefile.

Comment 1 Prarit Bhargava 2008-08-26 13:07:54 UTC
Created attachment 314994 [details]
patch v2

Comment 2 RHEL Program Management 2008-09-03 13:09:59 UTC
Updating PM score.

Comment 4 Linda Wang 2009-04-08 20:12:04 UTC
This is an internal infrastructure git request.. not 4.8 bug fix or customer issue. So, I am going to remove it from rhel4.8 and clear all other flags.

Comment 5 Jiri Pallich 2012-06-20 16:17:24 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.


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