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

Re: [RFC] Issues around C rebase--interactive

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Feb 17, 2008, 19:34 UTC
Message-ID
<alpine.LSU.1.00.0802171932470.30505@racer.site>
In-Reply-To
<alpine.LNX.1.00.0802171347060.5816@iabervon.org>
Hi,
On Sun, 17 Feb 2008, Daniel Barkalow wrote:
> There's a lot of stuff stored presently in ways that are convenient for 
> shell scripts and inconvenient for C.

We could have both, actually. There could be a ".git/state" to tell git abort/resume what the current actions are, and in addition the files that used to be there, too.

> Is anything else depending on the contents or location of 
> ".git/.dotest-merge"?

This has been discussed recently. I offered the opinion that some people's scripts might rely on the location, but was all but shot down. I guess we'll have to change it to find out.

Ciao, Dscho

Previous: Daniel BarkalowNext: Junio C Hamano
Message 2 of 3 in “[RFC] Issues around C rebase--interactive”
  1. Daniel BarkalowFeb 17, 2008
  2. Johannes SchindelinFeb 17, 2008
  3. Junio C HamanoFeb 17, 2008

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.