... | @@ -69,7 +69,7 @@ The Trac bug report system has various fields. Here's how to fill them in: |
... | @@ -69,7 +69,7 @@ The Trac bug report system has various fields. Here's how to fill them in: |
|
|
|
|
|
- **CC**. If you are only logged in as *guest* then please consider including your email address (using a comma or space as separator, not a semicolon). That way we can ask you questions, and you'll get email from Trac when something happens to your bug.
|
|
- **CC**. If you are only logged in as *guest* then please consider including your email address (using a comma or space as separator, not a semicolon). That way we can ask you questions, and you'll get email from Trac when something happens to your bug.
|
|
|
|
|
|
- **Component**, **Version**, **Operating system**, **Architecture** all help to describe the setup that failed. Please pay particular attention to **version**, which is the version of GHC that you are running.
|
|
- **Component**, **Version**, **Operating system**, **Architecture** all help to describe the setup that failed. Please pay particular attention to **version**, which is the version of GHC that you are running. Ideally, the version field is used to denote the first version a bug/issue is known to exist in (regardless whether that version is "supported" or not).
|
|
|
|
|
|
- **Priority**, **Milestone**, **Assign to**, **Difficulty**, **Test case**, **Blocking**, **Blocked by**: these are all for use by GHC developers; please don't fill these in.
|
|
- **Priority**, **Milestone**, **Assign to**, **Difficulty**, **Test case**, **Blocking**, **Blocked by**: these are all for use by GHC developers; please don't fill these in.
|
|
|
|
|
... | | ... | |