From: Peter Oberndorfer <kumbayo84@arcor.de>
To: "Karl Hasselström" <kha@treskal.com>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: [STG PATCH] change usage string of refresh to not refer to removed options
Date: Tue, 8 Jan 2008 21:43:53 +0100 [thread overview]
Message-ID: <200801082143.53125.kumbayo84@arcor.de> (raw)
for changing the patch author, commiter and description
Signed-off-by: Peter Oberndorfer <kumbayo84@arcor.de>
---
I saw this while doing the refresh --index patch.
There was a discussion about bringing back refresh -e
If that also brings back this options, please do not apply the patch:-)
stgit/commands/refresh.py | 8 +++-----
1 files changed, 3 insertions(+), 5 deletions(-)
diff --git a/stgit/commands/refresh.py b/stgit/commands/refresh.py
index 952b1b6..4695c62 100644
--- a/stgit/commands/refresh.py
+++ b/stgit/commands/refresh.py
@@ -31,11 +31,9 @@ usage = """%prog [options] [<files or dirs>]
Include the latest tree changes in the current patch. This command
generates a new GIT commit object with the patch details, the previous
-one no longer being visible. The patch attributes like author,
-committer and description can be changed with the command line
-options. The '--force' option is useful when a commit object was
-created with a different tool but the changes need to be included in
-the current patch."""
+one no longer being visible. The '--force' option is useful
+when a commit object was created with a different tool
+but the changes need to be included in the current patch."""
directory = DirectoryHasRepository()
options = [make_option('-f', '--force',
--
1.5.4.rc2
next reply other threads:[~2008-01-08 20:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 20:43 Peter Oberndorfer [this message]
2008-01-09 7:20 ` [STG PATCH] change usage string of refresh to not refer to removed options Karl Hasselström
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200801082143.53125.kumbayo84@arcor.de \
--to=kumbayo84@arcor.de \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox