From: Eric Lesh <eclesh@ucla.edu>
To: jsipek@cs.sunysb.edu
Cc: git <git@vger.kernel.org>
Subject: [PATCH guilt] Documentation/guilt-fork: document argument to choose name of new patch
Date: Tue, 27 Mar 2007 20:48:13 -0700 [thread overview]
Message-ID: <1175053693.5945.13.camel@localhost> (raw)
From: Eric Lesh <eclesh@ucla.edu>
Date: Tue, 27 Mar 2007 20:36:27 -0700
Subject: [PATCH] Documentation/guilt-fork: document argument to choose name of new patch
Signed-off-by: Eric Lesh <eclesh@ucla.edu>
---
Documentation/guilt-fork.txt | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/Documentation/guilt-fork.txt b/Documentation/guilt-fork.txt
index c5b9ed3..c474345 100644
--- a/Documentation/guilt-fork.txt
+++ b/Documentation/guilt-fork.txt
@@ -14,6 +14,11 @@ DESCRIPTION
Create a copy of the top most patch, and replace the entry in the series
file to use this new patch file.
+OPTIONS
+-------
+<new_name>::
+ The name of the new patch to create.
+
Author
------
Written by Josef "Jeff" Sipek <jsipek@cs.sunysb.edu>
--
1.5.1-rc1.GIT
reply other threads:[~2007-03-28 4:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1175053693.5945.13.camel@localhost \
--to=eclesh@ucla.edu \
--cc=git@vger.kernel.org \
--cc=jsipek@cs.sunysb.edu \
/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;
as well as URLs for NNTP newsgroup(s).