|
Size: 966
Comment:
|
Size: 840
Comment: fix `hg -d` switch to `hg --debug`
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| Report it to the mercurial mailing list, mercurial@selenic.com or in the bug tracker http://www.selenic.com/mercurial/bts/ |
Report it to the Mercurial mailing list at mercurial@selenic.com or in the [[ http://bz.selenic.com | bug tracker]]. |
| Line 11: | Line 9: |
| using the hg -v and hg -d switches to figure out exactly what | using the '`hg -v`' and '`hg --debug`' switches to figure out exactly what |
| Line 21: | Line 19: |
| If you'd like to request a feature, send your request to mercurial@selenic.com. As Mercurial is still very new, there are certainly features it is missing and you can give us feedback on how best to implement them. |
If you'd like to request a feature, please send your request to mercurial@selenic.com. |
I found a bug, what do I do?
Report it to the Mercurial mailing list at mercurial@selenic.com or in the bug tracker.
What should I include in my bug report?
Enough information to reproduce or diagnose the bug. If you can, try using the 'hg -v' and 'hg --debug' switches to figure out exactly what Mercurial is doing.
If you can reproduce the bug in a simple repository, that is very helpful. The best is to create a simple shell script to automate this process, which can then be added to our test suite.
Can Mercurial do <x>?
If you'd like to request a feature, please send your request to mercurial@selenic.com.
Be sure to see ToDo and MissingFeatures to see what's already planned and where we need help.