Make documentation less confusing

It's not just by default "stg new" doesn't do a refresh -- it never
does.

Signed-off-by: Karl Hasselström <kha@treskal.com>

diff --git a/stgit/commands/new.py b/stgit/commands/new.py
index 49c729d5e5c4412185c109da206deeeba15807cb..6a8f08630a548f9996227155694e791ecb597fdf 100644 (file)
--- a/stgit/commands/new.py
+++ b/stgit/commands/new.py
@@ -31,9 +31,9 @@ Create a new, empty patch and make it the topmost one. If the
 '--message' option is not passed, an editor is invoked with the
 .git/patchdescr.tmpl, ~/.stgit/templates/patchdescr.tmpl or
 /usr/share/stgit/templates/patchdescr.tmpl file used a as template,
-together with generated lines. By default, the local changes in the
-working tree are not included in the patch. A 'refresh' command is
-needed for this.
+together with generated lines. The local changes in the working tree
+are not included in the patch; an "stg refresh" command is needed for
+this.
 
 If no name is given for the new patch, one is generated from the first
 line of the commit message."""