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

Re: A couple of rebase --autosquash proposals

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 9, 2013, 20:20 UTC
Message-ID
<xmqq1u1lzshd.fsf@gitster.dls.corp.google.com>
In-Reply-To
<52A56887.4070909@viscovery.net>
Johannes Sixt <j.sixt@viscovery.net> writes:
Show 7 quoted lines
> Am 12/9/2013 3:23, schrieb Brett Randall:
>> * fixup! or squash! on it's own would default to fixing-up the
>> previous commit (or result of previous step of rebase if that was a
>> squash/fixup).
>
> Why would you want that? To fixup the previous commit, just use 'git
> commit --amend'. What am I missing?
When you are not absolutely sure if the amend is a good thing to do.
Then
	work work work
        git commit --fixup HEAD
	work work work
        git commit --fixup HEAD^
	work work work
        git commit --fixup HEAD^^
	...
	git rebase --autosquash -i ...
may become a good way to polish a single commit.
Previous: Brett RandallNext: Brett Randall
Message 6 of 7 in “A couple of rebase --autosquash proposals”
  1. Brett RandallDec 9, 2013
  2. Johannes SixtDec 9, 2013
  3. Chris PackhamDec 9, 2013
  4. Philippe VaucherDec 9, 2013
  5. Brett RandallDec 9, 2013
  6. Junio C HamanoDec 9, 2013
  7. Brett RandallDec 9, 2013

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.