From a838c1fb70c8ea8ec2c580325f660c9f1661b176 Mon Sep 17 00:00:00 2001 From: Alain Reguera Delgado Date: Oct 16 2011 21:25:13 +0000 Subject: Update `Preface/feedback.docbook'. --- diff --git a/Manuals/Tcar-ug/Preface/feedback.docbook b/Manuals/Tcar-ug/Preface/feedback.docbook index 96e97a6..6cbf3fd 100644 --- a/Manuals/Tcar-ug/Preface/feedback.docbook +++ b/Manuals/Tcar-ug/Preface/feedback.docbook @@ -3,45 +3,13 @@ Send In Your Feedback - When you find a bug in &TCAR; we want to hear about it. The - following suggestions are intended to assist you in forming - bug reports that can be handled in an effective fashion. No - one is required to follow them but doing so tends to be to - everyone's advantage. + If you find a bug in &TCAR; or this manual, we would like to + hear about it. To report bugs related to this manual, send an + e-mail to the sig-artwork@projects.centos.org + mailing list. When you write the bug report, take care of + being specific about the problem you are reporting on (e.g., + where it is, the section number, etc.) so we can found it + easily. - - We cannot promise to fix every error or implement every - feature right away. If a problem is obvious, critical, or - affects a lot of users, chances are good that someone will - look into it. It could also happen that we tell you to update - your working copy to a newer revision to see if the problem - happens there. Or we might decide that the problem cannot be - fixed before some major rewrite we might be planning is done. - Or perhaps it is simply too hard and there are more important - things on the agenda. If you need help immediately, consider - obtaining a commercial support contract. - - -
- Identifying Bugs - - ... - -
- -
- What To Report - - ... - -
- -
- Where To Report Bugs - - ... - -
-