|
Size: 840
Comment: fix `hg -d` switch to `hg --debug`
|
← Revision 6 as of 2017-02-06 05:31:02 ⇥
Size: 838
Comment: update links
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| Report it to the Mercurial mailing list at mercurial@selenic.com or in the [[ http://bz.selenic.com | bug tracker]]. | Report it to the Mercurial mailing list at mercurial@mercurial-scm.org or in the [[BugTracker|bug tracker]]. |
| Line 20: | Line 20: |
| mercurial@selenic.com. | mercurial@mercurial-scm.org. |
I found a bug, what do I do?
Report it to the Mercurial mailing list at mercurial@mercurial-scm.org 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@mercurial-scm.org.
Be sure to see ToDo and MissingFeatures to see what's already planned and where we need help.