[or-cvs] r8300: Prepare 0.1.2.1-alpha-1 (in tor/trunk: . debian)

[weasel@xxxxxxxx]

Author: weasel
Date: 2006-08-29 16:44:05 -0400 (Tue, 29 Aug 2006)
New Revision: 8300

Modified:
   tor/trunk/
   tor/trunk/debian/changelog
Log:
 r9567@galaxy:  weasel | 2006-08-29 22:32:46 +0200
 Prepare 0.1.2.1-alpha-1



Property changes on: tor/trunk
___________________________________________________________________
 svk:merge ticket from /local/or/tor/trunk [r9567] on 1f724f9b-111a-0410-b636-93f1a77c1813

Modified: tor/trunk/debian/changelog
===================================================================
--- tor/trunk/debian/changelog	2006-08-29 20:43:59 UTC (rev 8299)
+++ tor/trunk/debian/changelog	2006-08-29 20:44:05 UTC (rev 8300)
@@ -1,6 +1,5 @@
-tor (0.1.2.0-alpha-cvs-1) unstable; urgency=low
+tor (0.1.2.1-alpha-1) unstable; urgency=low
 
-  * CVS snapshot.
   * Forward port 07_log_to_file_by_default.dpatch.
   * Previously our defaults for DataDirectory, PidFile, RunAsDaemon, and
     Log differed from upstreams.  Now Tor behaves just like before (with
@@ -10,8 +9,10 @@
   * Tell users about the init script when they try to run Tor as root.
     Should we also do this when they try to run their Tor as any other
     (non root, non debian-tor) user? - add 11_tor_as_root_more_helpful
+  * Use tor --verify-config before start and reload.  Abort init script
+    with exit 1 if config does not verify.
 
- -- Peter Palfrader <weasel@xxxxxxxxxx>  Mon, 24 Jul 2006 05:37:17 +0200
+ -- Peter Palfrader <weasel@xxxxxxxxxx>  Tue, 29 Aug 2006 22:32:29 +0200
 
 tor (0.1.1.23-XXXXXX) unstable; urgency=low