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

[GSoC update] Sequencer: Dealing with historical mistakes

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Aug 18, 2011, 19:15 UTC
Message-ID
<CALkWK0mzhWqsc15ufWPB5_aJmPVmrfmxOFyU33i9XbWvFK0N=A@mail.gmail.com>
Hi,

Junio suddenly raised some very disturbing concerns about the overall UI consistency wrt '--continue'. I'm really glad he raised it before we locked ourselves into yet another UI mistake. Work on the generalized sequencer series has totally halted since, and I've been pondering about what to do. After some thought, I've tried to untangle the various issues and add something useful to the discussion [1]. I'm somewhat annoyed that we're stuck with these historical mistakes, and I hope that our future design isn't constrained too badly.

Otherwise, I've requested Junio to merge 'rr/cherry-pick-continue' as-it-is, since it doesn't have any major issues. The generalized sequencer series itself will take some more time- we have to decide the final implementation details at the end of the discussion. Also, the GSoC is drawing to a close, and I plan to post a somewhat elaborate final update. If there's something in particular you'd like to see in it, do let me know.

Thanks for reading.
[1]: http://mid.gmane.org/CALkWK0noHBnW-7zZLw=jJdDVFxXmsm2vHHYnUJc9miLLuDRnAg@mail.gmail.com
-- Ram
Message 1 of 1 in “[GSoC update] Sequencer: Dealing with historical mistakes”
  1. Ramkumar RamachandraAug 18, 2011

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.