From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH 0/3] Return of "add -p [E]dit" fix
Date: Fri, 29 Apr 2011 15:49:30 -0700 [thread overview]
Message-ID: <1304117373-592-1-git-send-email-gitster@pobox.com> (raw)
I kept this in the stalled state for too long. Resending with tests
to move the topic forward.
Junio C Hamano (3):
t3701: Editing a split hunk in an "add -p" session
add--interactive.perl: factor out repeated --recount option
"add -p": work-around an old laziness that does not coalesce hunks
builtin/apply.c | 9 ++++++---
git-add--interactive.perl | 16 ++++++++--------
t/t3701-add-interactive.sh | 36 ++++++++++++++++++++++++++++++++++++
3 files changed, 50 insertions(+), 11 deletions(-)
--
1.7.5.252.g565191
next reply other threads:[~2011-04-29 22:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 22:49 Junio C Hamano [this message]
2011-04-29 22:49 ` [PATCH 1/3] t3701: Editing a split hunk in an "add -p" session Junio C Hamano
2011-04-29 22:49 ` [PATCH 2/3] add--interactive.perl: factor out repeated --recount option Junio C Hamano
2011-04-29 22:49 ` [PATCH 3/3] "add -p": work-around an old laziness that does not coalesce hunks Junio C Hamano
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=1304117373-592-1-git-send-email-gitster@pobox.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/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).