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

Re: [BUG?] rebase -i: edit versus unmerged changes

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 22, 2013, 20:42 UTC
Message-ID
<7vehf76uai.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20130322182550.GF12223@google.com>
Jonathan Nieder <jrnieder@gmail.com> writes:
Show 10 quoted lines
> Ramkumar Ramachandra wrote:
>
>> I'd really to have that final 'git continue' in Git 2.0.  Can someone
>> attempt to break up the migration path into manageable logical steps
>> that we can start working on?
>
> Is there any deadline or migration path needed?  Depending on the
> design, it might be possible to do without backward-incompatible
> changes, meaning the migration path is "whatever someone feels like
> implementing first lands first".

FWIW, I am not convinced yet why we would even want "git continue" in the first place, so I won't be the one who would be suggesting a migration path.

Previous: Jonathan NiederNext: Ramkumar Ramachandra
Message 8 of 10 in “[BUG?] rebase -i: edit versus unmerged changes”
  1. Ramkumar RamachandraMar 19, 2013
  2. Andrew WongMar 19, 2013
  3. Ramkumar RamachandraMar 20, 2013
  4. Jonathan NiederMar 20, 2013
  5. Junio C HamanoMar 20, 2013
  6. Ramkumar RamachandraMar 22, 2013
  7. Jonathan NiederMar 22, 2013
  8. Junio C HamanoMar 22, 2013
  9. Ramkumar RamachandraMar 23, 2013
  10. Junio C HamanoMar 24, 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.