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

Re: [REQ] Better error reporting when git rebase cannot rebase

From
Jake Goulding <goulding@vivisimo.com>
Date
Apr 3, 2008, 13:38 UTC
Message-ID
<47F4DDDB.60706@vivisimo.com>
In-Reply-To
<20080403095722.GA6673@coredump.intra.peff.net>
Jeff King wrote:
Show 7 quoted lines
> 
> Unfortunately I am not sure of the best way to fix this message. It
> happens at a very low level in read-cache.c, and so it shows up in
> several different places. I am not even sure of all the places you can
> see it, so coming up with different text that makes more sense is
> non-trivial.
>

I was afraid that something like that might be the case. Would it be worth putting in a second request to make that message more specific?

> But this is, I think, a slightly separate issue, which is that rebase
> just bails without saying why. And that's easy to fix. How about this?
> 
 > [.snip.]

That seems good to me. I think the important thing is to make sure that the user is aware that what they wanted to do did not happen.

Previous: Jeff King
Message 3 of 3 in “[REQ] Better error reporting when git rebase cannot rebase”
  1. Jake GouldingApr 2, 2008
  2. Jeff KingApr 3, 2008
  3. Jake GouldingApr 3, 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.