From: Bram Schoenmakers <me@bramschoenmakers.nl>
To: git@vger.kernel.org, gitster@pobox.com
Subject: [PATCH] Mention split command in git-add manpage
Date: Sat, 20 Oct 2007 21:15:08 +0200 [thread overview]
Message-ID: <200710202115.10028.me@bramschoenmakers.nl> (raw)
Hello,
A little patch for the git-add manpage which mentions the 's' option for
splitting hunks in git-add -i mode.
---
Documentation/git-add.txt | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-add.txt b/Documentation/git-add.txt
index 2fe7355..032957a 100644
--- a/Documentation/git-add.txt
+++ b/Documentation/git-add.txt
@@ -210,6 +210,7 @@ patch::
k - do not decide on this hunk now, and view the previous
undecided hunk
K - do not decide on this hunk now, and view the previous hunk
+ s - split large hunks at context lines in the middle
+
After deciding the fate for all hunks, if there is any hunk
that was chosen, the index is updated with the selected hunks.
--
1.5.2.5
Kind regards,
--
Bram Schoenmakers
You can contact me directly on ICQ with #153817629
reply other threads:[~2007-10-20 19: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=200710202115.10028.me@bramschoenmakers.nl \
--to=me@bramschoenmakers.nl \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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;
as well as URLs for NNTP newsgroup(s).