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

Re: [RFH] rebase -i optimization

From
Sverre Rabbelier <srabbelier@gmail.com>
Date
Feb 27, 2009, 12:29 UTC
Message-ID
<fabb9a1e0902270429t5d31aaaet1e8c07e2b42751c3@mail.gmail.com>
In-Reply-To
<alpine.DEB.1.00.0902271146460.6600@intel-tinevez-2-302>
Heya,

On Fri, Feb 27, 2009 at 11:50, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

> On one hand, I could imagine that it is just a question of skipping those
> 'pick' commands that do not contribute anything.  That would be a pretty
> simple function that would be called at the very beginning.
Exactly, that's what I had in mind.
> On the other hand, this very simple strategy would fail pretty quickly
> (and badly) with -i -p.  And that is the stuff I am mostly spending my Git
> time budget on these days.

I would be fine with making this optimization optional (with a config option?), and barf if both the optimization and -p are supplied. We could even automagically ignore the config option for -p, and only barf if both -p and this option are specified explicitly?

> Having said that, I think yours might be such a common case that it is
> worth optimizing for.

Does this fit in your git time budget, or would you prefer I have a stab at it? If the latter, any hints on where to put such a call?

-- 
Cheers,

Sverre Rabbelier
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 5 of 16 in “[RFH] rebase -i optimization”
  1. Sverre RabbelierFeb 26, 2009
  2. Johannes SchindelinFeb 26, 2009
  3. Sverre RabbelierFeb 26, 2009
  4. Johannes SchindelinFeb 27, 2009
  5. Sverre RabbelierFeb 27, 2009
  6. rebase -i: avoid 'git reset' when possibleJohannes Schindelin, Feb 27, 2009
  7. Sverre RabbelierFeb 27, 2009
  8. Johannes SchindelinFeb 27, 2009
  9. Junio C HamanoMar 1, 2009
  10. Johannes SchindelinMar 1, 2009
  11. Junio C HamanoMar 3, 2009
  12. Johannes SchindelinMar 3, 2009
  13. rebase -i: avoid 'git reset' when possibleJohannes Schindelin, Mar 3, 2009
  14. Johannes SixtMar 3, 2009
  15. Johannes SchindelinMar 3, 2009
  16. Sitaram ChamartyFeb 27, 2009

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.