Bug 1826

Summary: xorgcfg genererate xorg.conf-4 file
Product: xorg Reporter: Matthieu Herrb <matthieu.herrb>
Component: App/xorgcfgAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: high CC: roland.mainz
Version: 6.8.1   
Hardware: Other   
OS: OpenBSD   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
[FIXED_X11R68x] patch roland.mainz: 6.8-branch+

Description Matthieu Herrb 2004-11-11 07:16:15 UTC
xf86cfg generates the XF86Config-4 file by default. 
when transitioning from XF86config to xorg.conf the code that adds the '-4' 
suffix was not removed.
Comment 1 Matthieu Herrb 2004-11-11 07:17:17 UTC
Created attachment 1283 [details] [review]
[FIXED_X11R68x] patch
Comment 2 Roland Mainz 2004-11-12 08:32:29 UTC
Comment on attachment 1283 [details] [review]
[FIXED_X11R68x] patch

Approved for checkin into X11R6.8.x in the 2004-11-12 release-wranglers call.
Comment 3 Roland Mainz 2004-12-14 19:11:07 UTC
Comment on attachment 1283 [details] [review]
[FIXED_X11R68x] patch

Patch checked-in into X11R6.8.x stzable branch:

/cvs/xorg/xc/ChangeLog,v  <--  ChangeLog
new revision: 1.365.2.69; previous revision: 1.365.2.68
cvs commit: Using deprecated info format strings.  Convert your scripts to use
the new argument format and remove '1's from your info file format strings.
/cvs/xorg/xc/programs/Xserver/hw/xfree86/xf86cfg/interface.c,v	<-- 
interface.c
new revision: 1.2.4.1; previous revision: 1.2
cvs commit: Using deprecated info format strings.  Convert your scripts to use
the new argument format and remove '1's from your info file format strings.
Mailing the commit message to xorg-commit@lists.freedesktop.org...
Comment 4 Roland Mainz 2004-12-14 19:12:26 UTC
Patch checked-in into Xorg trunk and X11R6.8.x stable branch...

... marking bug as FIXED (plese reopen if there are any outstanding/unresolved
issues).

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.