From: Sverre Rabbelier <srabbelier@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: trast@student.ethz.ch, git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: [PATCH] add -i: ignore terminal escape sequences
Date: Tue, 17 May 2011 21:37:50 -0700 [thread overview]
Message-ID: <BANLkTinSKFVP=VYw4PoLP=-AUbLKeGX+gQ@mail.gmail.com> (raw)
In-Reply-To: <7vipt8fyxj.fsf@alter.siamese.dyndns.org>
Heya,
On Tue, May 17, 2011 at 20:52, Junio C Hamano <gitster@pobox.com> wrote:
> Jokes aside, it may make sense to offer an extra confirmation for "a" and
> possibly "s" in single-key mode. Unlike others, they are destructive when
> the changes you are splitting from the working tree is large-ish.
I don't understand why/how 's' is destructive? Doesn't it just ask you
again for each of the split hunks?
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2011-05-18 4:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 15:19 [PATCH] add -i: ignore terminal escape sequences trast
2011-05-18 3:52 ` Junio C Hamano
2011-05-18 4:37 ` Sverre Rabbelier [this message]
2011-05-18 5:03 ` Junio C Hamano
2011-05-18 5:54 ` Jeff King
2011-05-18 7:33 ` Thomas Rast
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='BANLkTinSKFVP=VYw4PoLP=-AUbLKeGX+gQ@mail.gmail.com' \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=trast@student.ethz.ch \
/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).