| Summary: | RFE: Bump version number in X11R6.8.x stable branch to X11R6.8.2, tag the tree and get it released. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Roland Mainz <roland.mainz> | ||||
| Component: | * Other | Assignee: | Roland Mainz <roland.mainz> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | high | CC: | eich, kem, roland.mainz | ||||
| Version: | 6.8.2 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
|
Description
Roland Mainz
2005-02-09 09:57:12 UTC
Created attachment 1879 [details] [review] [FIXED_X11R68x] Patch for 2005-02-09-XORG-6_8-branch Comment on attachment 1879 [details] [review] [FIXED_X11R68x] Patch for 2005-02-09-XORG-6_8-branch Patch checked-in into X11R6.8.x stable branch: /cvs/xorg/xc/ChangeLog,v <-- xc/ChangeLog new revision: 1.365.2.155; previous revision: 1.365.2.154 /cvs/xorg/xc/Makefile,v <-- xc/Makefile new revision: 1.4.2.1; previous revision: 1.4 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/xorgversion.def,v <-- xc/config/cf/xorgversion.def new revision: 1.1.4.6; previous revision: 1.1.4.5 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... X11R6.8.2 final was tagged like this: % export CVSROOT=:ext:hackedaccount@cvs.freedesktop.org:/cvs/xorg % export CVS_RSH=ssh % cvs -z8 checkout -r XORG-6_8-branch xc % cvs -z1 tag XORG-6_8_2 xc The release canidate can be checked-out like this: % export CVSROOT=:pserver:anoncvs@cvs.freedesktop.org:/cvs/xorg % cvs -z8 checkout -r XORG-6_8_2 xc X11R6.8.2 is out since a while... marking bug as FIXED. |
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.