From b85450f9de77183fd9fc7900bb0d290adaaaf9fd Mon Sep 17 00:00:00 2001 Message-Id: From: Mark Wooding Date: Mon, 24 Mar 2008 18:50:47 +0000 Subject: [PATCH] Make documentation less confusing MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit Organization: Straylight/Edgeware From: Karl Hasselström It's not just by default "stg new" doesn't do a refresh -- it never does. Signed-off-by: Karl Hasselström --- stgit/commands/new.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/stgit/commands/new.py b/stgit/commands/new.py index 49c729d..6a8f086 100644 --- 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.""" -- [mdw]