---

yaml
---
r: 157439
b: refs/heads/snap-stage3
c: 091b981
h: refs/heads/master
i:
  157437: 56f5256
  157435: ce97ec0
  157431: bf3c65a
  157423: 22838f5
  157407: ab9b619
  157375: 19f243b
  157311: 0cdc423
  157183: 648ccd8
v: v3

Author: bors

[refs]

@@ -1,7 +1,7 @@
 ---
 refs/heads/master: 065caf34f5ff29e04605f95d9c5d511af219439a
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
-refs/heads/snap-stage3: 4a74af62c627df259f0e0a6d523f71b7cae749d0
+refs/heads/snap-stage3: 091b9811c83d545a56a8dea8cbf9e9a2a39caa3c
 refs/heads/try: 0ee4d8b0b112c608646fa75463ab4dc59132efd9
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/heads/ndm: f3868061cd7988080c30d6d5bf352a5a5fe2460b

branches/snap-stage3/src/doc/complement-bugreport.md

@@ -33,9 +33,21 @@ miss out on valid bug reports.
 
 It generally helps our diagnosis to include your specific OS (for example: Mac OS X 10.8.3,
 Windows 7, Ubuntu 12.04) and your hardware architecture (for example: i686, x86_64).
-It's also helpful to copy/paste the output of re-running the erroneous rustc
-command with the `-v` flag. Finally, if you can run the offending command under gdb,
-pasting a stack trace can be useful; to do so, you will need to set a breakpoint on `rust_fail`.
+It's also helpful to provide the exact version and host by copying the output of
+re-running the erroneous rustc command with the `--version=verbose` flag, which will
+produce something like this:
+
+```{ignore}
+rustc 0.12.0 (ba4081a5a 2014-10-07 13:44:41 -0700)
+binary: rustc
+commit-hash: ba4081a5a8573875fed17545846f6f6902c8ba8d
+commit-date: 2014-10-07 13:44:41 -0700
+host: i686-apple-darwin
+release: 0.12.0
+```
+
+Finally, if you can run the offending command under gdb, pasting a stack trace can be
+useful; to do so, you will need to set a breakpoint on `rust_fail`.
 
 # I submitted a bug, but nobody has commented on it!