You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
-
3Great answer! Email is better known than issue trackers, and easier to understand (which is not to say everyone "gets" email :P )Andres F.– Andres F.2013-03-26 15:59:56 +00:00Commented Mar 26, 2013 at 15:59
-
27Also, that GNU advice is ancient, way older than the web and web-based issue trackers.Ross Patterson– Ross Patterson2013-03-27 00:24:40 +00:00Commented Mar 27, 2013 at 0:24
-
6@gnat: A major part of that linked answer being so great is the "if it's easy for you, you can enter that sort of thing right there" part. That is key to many open source projects, as there is no funding for phone support. A mailing list is a turn-off for me as a bug-reporting user, as I don't want to have to sign up for responses. With a bug tracker, I can see that the issue I have is in the system, and can come back and search for it later, and see if it's been updated. This is difficult with a mailing list, unless there is a really good web-based list tracker, which often isn't the case.naught101– naught1012013-03-30 13:08:00 +00:00Commented Mar 30, 2013 at 13:08
-
1@naught101 It might not be older than the Web but it's definitely older than Web-based trackerssakisk– sakisk2013-10-16 14:11:43 +00:00Commented Oct 16, 2013 at 14:11
-
2@chris for the matters of issue tracking, mail is not really convenient... "in the mail you sent us two months ago, you mentioned... no not that email, you sent us five emails this day, three of them were with subject Re: blue button click, look at the second one, the one with 10Mb screen shot attached to it... what? you can't find it?"gnat– gnat2015-12-31 18:40:42 +00:00Commented Dec 31, 2015 at 18:40
|
Show 2 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you