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

Re: what is a 'sequencer'

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 24, 2012, 01:59 UTC
Message-ID
<xmqqzka1hotv.fsf@junio.mtv.corp.google.com>
In-Reply-To
<jn4vrk$98c$1@dough.gmane.org>
Neal Kreitzinger <nkreitzinger@gmail.com> writes:
> All the talk about git 'sequencer' sounds interesting, but I don't
> know what it is.  (web search didn't help.)  Is there an explanation
> somewhere on what its supposed to do?
The sequencer is what sequences a sequence of operations ;-).

As an end user, stare at the instruction sheet "rebase -i" lets you edit, and imagine different possibilities other than those offered by "rebase -i" (e.g. "build on top of the history by cherry picking this commit", "cherry pick this commit without committing, and amend the top of of the history").

For example, wouldn't it be nice if you could say "here is a mbox---run am to slurp the patches into commit and build history", or "merge the history leading to this commit"? "mark this point as :1, checkout this other commit and continue operation"? "now merge the commit we marked earlier as :1 to the history"? What other vocabularies can you imagine to enrich your git life?

Recent additions to let "cherry-pick" and "revert" replay and revert multiple commits are indeed built on the nascent version of this infrastructure.

Previous: Neal Kreitzinger
Message 2 of 2 in “what is a 'sequencer'”
  1. Neal KreitzingerApr 24, 2012
  2. Junio C HamanoApr 24, 2012

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.