[Monotone-commits-diffs] net.venge.monotone: 1f323fadb24c032518db433178c7cc757914a564

[code]

revision:            1f323fadb24c032518db433178c7cc757914a564
date:                2012-07-23T09:14:07
author:              address@hidden
branch:              net.venge.monotone
changelog:
* innosetup/README.txt: add coment about ensuring base revision is in executable

manifest:
format_version "1"

new_manifest [bdad16ac54631abb2b79dc08997e730c9cb38370]

old_revision [83155202b010fec62428f5970acf40738930ff42]

patch "innosetup/README.txt"
 from [6f92ce9f01c75b83994b690bb8b00c549c368965]
   to [d306d15f4bba8011dd1fa01dd9522b93c8ce8920]
============================================================
--- innosetup/README.txt	6f92ce9f01c75b83994b690bb8b00c549c368965
+++ innosetup/README.txt	d306d15f4bba8011dd1fa01dd9522b93c8ce8920
@@ -19,6 +19,10 @@
 Check out the release version of monotone:
 mtn -d /path/to/monotone.db checkout -r t:monotone-<version> --branch net.venge.monotone.monotone-<version> monotone-<version>
 
+Do not use the source tarball; if you do, the resulting monotone
+executable will not know the base revision, which is needed for good
+bug reports.
+
 Build the release. See the last instruction in ../INSTALL_windows_native.txt
 Then build the installer: