| Summary: | RFE: Bump the version number to X116.8.1.903 and get X11R6.8.2RC3 shipped. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Roland Mainz <roland.mainz> | ||||
| Component: | * Other | Assignee: | Roland Mainz <roland.mainz> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | high | CC: | roland.mainz | ||||
| Version: | 6.8.2 | ||||||
| Hardware: | SPARC | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
|
Description
Roland Mainz
2005-01-25 08:20:16 UTC
Created attachment 1747 [details] [review] Patch for 2005-01-25-XORG-6_8-branch to update the version number Comment on attachment 1747 [details] [review] Patch for 2005-01-25-XORG-6_8-branch to update the version number Approving patch myself to get the version number bumped. attachment #1747 [details] [review] checked-in: /cvs/xorg/xc/ChangeLog,v <-- ChangeLog new revision: 1.365.2.138; previous revision: 1.365.2.137 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 <-- xorgversion.def new revision: 1.1.4.4; previous revision: 1.1.4.3 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.2RC3 has been 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_1_903 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_1_903 xc RC3 is out since a while and RC4 will be tagged and released in an hour... ... 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.