171 |
171 |
172 Patches to support Windows are being actively integrated, a fully |
172 Patches to support Windows are being actively integrated, a fully |
173 working Windows version is probably not far off |
173 working Windows version is probably not far off |
174 |
174 |
175 |
175 |
176 Section 2: Technical |
176 Section 2: Bugs and Features |
|
177 ---------------------------- |
|
178 |
|
179 .Q. I found a bug, what do I do? |
|
180 |
|
181 Report it to the mercurial mailing list, mercurial@selenic.com. |
|
182 |
|
183 |
|
184 .Q. What should I include in my bug report? |
|
185 |
|
186 Enough information to reproduce or diagnose the bug. If you can, try |
|
187 using the hg -v and hg -d switches to figure out exactly what |
|
188 Mercurial is doing. |
|
189 |
|
190 If you can reproduce the bug in a simple repository, that is very |
|
191 helpful. The best is to create a simple shell script to automate this |
|
192 process, which can then be added to our test suite. |
|
193 |
|
194 |
|
195 .Q. Can Mercurial do <x>? |
|
196 |
|
197 If you'd like to request a feature, send your request to |
|
198 mercurial@selenic.com. As Mercurial is still very new, there are |
|
199 certainly features it is missing and you can give up feedback on how |
|
200 best to implement them. |
|
201 |
|
202 |
|
203 Section 3: Technical |
177 -------------------- |
204 -------------------- |
178 |
205 |
179 .Q. What limits does Mercurial have? |
206 .Q. What limits does Mercurial have? |
180 |
207 |
181 Mercurial currently assumes that single files, indices, and manifests |
208 Mercurial currently assumes that single files, indices, and manifests |