| Summary: | bogus contact addresses in Xserver/os/utils.c | ||
|---|---|---|---|
| Product: | xorg | Reporter: | Alan Coopersmith <alan.coopersmith> |
| Component: | Server/General | Assignee: | Xorg Project Team <xorg-team> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | high | CC: | kem |
| Version: | 6.7.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Bug Depends on: | |||
| Bug Blocks: | 351 | ||
I agree. Personally, I like VendorSupportContact better than BuilderEmailAddr. It would be nice to create a separate "vendor.cf" file where all of the vendor specific configuration should go (e.g., release string, support contact, etc.). Let's bring this up on the next release wranglers' call to find out what the correct default should be. This change has been made and checked in. Closing. The contact address is used in the following order: 1. VendorSupportAddress 2. BuilderEMailAddr 3. "xorg@freedesktop.org" That is, if the first one is not defined, then use the second and so on. |
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.
If you try to start the X server with an argument longer than 128 characters it tells you to mail "&&&&&@X.org" - checking Xserver/os/utils.c we see: #define ARGMSG \ "\nIf the arguments used are valid, and have been rejected incorrectly\n" \ "please send details of the arguments and why they are valid to\n" \ "&&&&&@X.org. In the meantime, you can start the Xserver as\n" \ "the \"super user\" (root).\n" #define ENVMSG \ "\nIf the environment is valid, and have been rejected incorrectly\n" \ "please send details of the environment and why it is valid to\n" \ "&&&&&@X.org. In the meantime, you can start the Xserver as\n" \ "the \"super user\" (root).\n" Perhaps these should be BuilderEmailAddr or some sort of VenderSupportContact define, with a default of xorg@freedesktop.org or something like that?