From: Robear Selwans <rwagih.rw@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC][GSOC] Microproject Suggestion
Date: Fri, 14 Feb 2020 09:29:33 +0200 [thread overview]
Message-ID: <CALH1-XruJ8UnHTN+xi=NOPtoP-p_F2OCmkLai8kjzsLObg=AvQ@mail.gmail.com> (raw)
In-Reply-To: <xmqqy2t6osht.fsf@gitster-ct.c.googlers.com>
On Fri, Feb 14, 2020 at 3:41 AM Junio C Hamano <gitster@pobox.com> wrote:
> For the feature itself, I'd just do
> $ git reset --soft HEAD~$n ;# rewind
> $ git commit --amend
>
> to open an editor, and then to the editor to edit the log message,
> I'd tell it to insert "git log ..@{1}" to the edit buffer to help me
> formulate the log message for the consolidated change, so I do not
> personally see me using it, even if it were available.
Yeah, this makes a lot of sense.
That was actually the only idea that I could come up with till now. I
am open to suggestions, though. I don't really mind if it is too big,
as I am also interested in contributing to git.
next prev parent reply other threads:[~2020-02-14 7:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 0:52 [RFC][GSOC] Microproject Suggestion Robear Selwans
2020-02-14 1:41 ` Junio C Hamano
2020-02-14 7:29 ` Robear Selwans [this message]
2020-02-14 8:49 ` Denton Liu
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='CALH1-XruJ8UnHTN+xi=NOPtoP-p_F2OCmkLai8kjzsLObg=AvQ@mail.gmail.com' \
--to=rwagih.rw@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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;
as well as URLs for NNTP newsgroup(s).