From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Dmitry Potapov <dpotapov@gmail.com>, git@vger.kernel.org
Subject: Re: git rebase interactive: usability issue
Date: Wed, 25 Jun 2008 20:32:04 -0700 [thread overview]
Message-ID: <7vbq1ovpl7.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0806260416410.4503@eeepc-johanness> (Johannes Schindelin's message of "Thu, 26 Jun 2008 04:17:55 +0200 (CEST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> NACK.
>
> You just broke the 'edit' command.
Really? I thought it would be Ok for "edit" command.
The patch checks the presense of /amend and complains only if it does not
exist, while you create /amend when you respond to "edit" insn.
I was relunctant about the patch not because of "edit", but because I am
not convinced that it will _never_ make sense to be able to amend while
the sequence stops with a conflict (as the patch does not give us any way
to override this rather heavy-handed denial to continue).
I also was hoping that with enough hooks git-commit already calls, this
could have been experimented and implemented with hooks without touching C
layer at least initially, while people can convince themselves that the
approach is sane (i.e. it _never_ makes sense to do amend upon conflict).
next prev parent reply other threads:[~2008-06-26 3:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 23:32 git rebase interactive: usability issue Dmitry Potapov
2008-06-26 2:17 ` Johannes Schindelin
2008-06-26 3:32 ` Junio C Hamano [this message]
2008-06-26 3:59 ` Avery Pennarun
2008-06-26 11:35 ` Dmitry Potapov
2008-06-26 12:13 ` Theodore Tso
2008-06-26 13:33 ` [PATCH v2] don't allow 'commit --amend' during rebase conflict resolution Dmitry Potapov
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=7vbq1ovpl7.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=dpotapov@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.