From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Sverre Rabbelier <srabbelier@gmail.com>,
trast@student.ethz.ch, git@vger.kernel.org
Subject: Re: [PATCH] add -i: ignore terminal escape sequences
Date: Wed, 18 May 2011 01:54:11 -0400 [thread overview]
Message-ID: <20110518055411.GA27482@sigill.intra.peff.net> (raw)
In-Reply-To: <7vei3weh2w.fsf@alter.siamese.dyndns.org>
On Tue, May 17, 2011 at 10:03:03PM -0700, Junio C Hamano wrote:
> I think "add -p" used to have an internal mechanism to merge the adjacent
> split hunks back to a single hunk, so if we wanted to we could have given
> users a way to recover from a mistaken "s"plit, but I don't think we kept
> that code, so there is no way to properly "recover" from such a mistake.
>
> Yes, it may be just the matter of two easy keystrokes, either yy or nn, to
> recover from such a mistake, and that is why I said "possibly". It is
> nevertheless destructive in the sense that you cannot recover without
> quitting the current session and restarting.
>
> Of course Thomas could have simply done "reset" and started from scratch,
> so in that sense nothing is destructive, but we are not talking about the
> kind of destructive operations you cannot possibly recover without typing
> everything again.
I'm not that concerned about these type of destructive operations, which
might waste a few seconds or a minute of your time. But Thomas' original
email indicated he was using "git checkout -p", which _is_ destructive
in a much bigger way, because a "y" overwrites worktree files which do
not otherwise have a backup (even "reset -p" leaves unreferenced blobs
that used to be in the index).
-Peff
next prev parent reply other threads:[~2011-05-18 5:54 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
2011-05-18 5:03 ` Junio C Hamano
2011-05-18 5:54 ` Jeff King [this message]
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=20110518055411.GA27482@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=srabbelier@gmail.com \
--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).