git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC][GSOC] Microproject Suggestion

From
Robear Selwans <rwagih.rw@gmail.com>
Date
Feb 14, 2020, 07:29 UTC
Message-ID
<CALH1-XruJ8UnHTN+xi=NOPtoP-p_F2OCmkLai8kjzsLObg=AvQ@mail.gmail.com>
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:
Show 8 quoted lines
> 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.

Previous: Junio C HamanoNext: Denton Liu
Message 3 of 4 in “[RFC][GSOC] Microproject Suggestion”
  1. Robear SelwansFeb 14, 2020
  2. Junio C HamanoFeb 14, 2020
  3. Robear SelwansFeb 14, 2020
  4. Denton LiuFeb 14, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.