From: Junio C Hamano <gitster@pobox.com>
To: Jean Privat <jean.privat@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] teach --edit to git rebase
Date: Tue, 11 Oct 2011 21:44:34 -0700 [thread overview]
Message-ID: <7vvcrubyz1.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: CAMQw0oOBEjW3yS2+wcktXDuEuUiHKjfbK2qDzKvBOiwxo7Zkow@mail.gmail.com
Jean Privat <jean.privat@gmail.com> writes:
> Yes I know "show me the code" but because I am lazy I prefer ask 1-if
> the proposal makes sense, and 2-if the following way of doing it makes
> sense.
No, no, and no we do not necessarily hate talking to lazy people but only
as long as what they propose makes some sense.
The only thing you can do with this new option is "update one commit
buried in the history, and rebase everything that build on top of it", as
far as I can tell. It feels a shame to waste the generic word "--edit" for
such a narrow option.
At the UI level, "git commit --amend HEAD~4" might be a more natural way
to invoke such an operation, I would think.
next prev parent reply other threads:[~2011-10-12 4:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 21:21 [RFC] teach --edit to git rebase Jean Privat
2011-10-11 22:36 ` Jean Privat
2011-10-12 4:44 ` Junio C Hamano [this message]
2011-10-12 13:57 ` Jean Privat
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=7vvcrubyz1.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jean.privat@gmail.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