Bug 1827

Summary: xf86site.def is referenced in comments in places where xorgsite.def is used
Product: xorg Reporter: Matthieu Herrb <matthieu.herrb>
Component: Build/MonolithicAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: high    
Version: 6.8.1   
Hardware: Other   
OS: OpenBSD   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
[FIXED_X11R68x] trivial patch roland.mainz: 6.8-branch+

Description Matthieu Herrb 2004-11-11 07:21:47 UTC
See attached patch
Comment 1 Matthieu Herrb 2004-11-11 07:22:16 UTC
Created attachment 1284 [details] [review]
[FIXED_X11R68x] trivial patch
Comment 2 Roland Mainz 2004-11-12 09:08:02 UTC
Comment on attachment 1284 [details] [review]
[FIXED_X11R68x] trivial patch

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

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

/cvs/xorg/xc/ChangeLog,v  <--  ChangeLog
new revision: 1.365.2.61; previous revision: 1.365.2.60
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/config/cf/xorgsite.def,v  <--  xorgsite.def
new revision: 1.10.2.2; previous revision: 1.10.2.1
/cvs/xorg/xc/config/cf/Attic/xprint_site.def,v	<--  xprint_site.def
new revision: 1.3.4.2; previous revision: 1.3.4.1
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 Adam Jackson 2005-04-03 14:35:45 UTC
mass update: the fix for this bug was applied to both HEAD and the stable 6.8 branch, but the bug was 
never closed.  closing now.

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.