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

RE: git-whatchanged -p anomoly?

From
Luck, Tony <tony.luck@intel.com>
Date
Aug 18, 2005, 22:44 UTC
Message-ID
<B8E391BBE9FE384DAA4C5C003888BE6F042C819D@scsmsx401.amr.corp.intel.com>
Show 8 quoted lines
>Now, I suspect you didn't mean to commit that thing: it really looks like 
>you've mixed up your patches somehow, because the commit message seems to 
>match only a very small portion of the patch.
>
>Did you perhaps have a failed merge or something that was in your index 
>when you applied that patch? If you have a dirty index when you do 
>"git-applymbox", it the commit done as part of the applymbox might commit 
>other state too.

Yes I had a failed merge ... I thought that I had cleaned up from it, but clearly I hadn't. Bother.

I guess I have a bit of tree maintenance to do ... But I think that it should be easy ... I can just step "test" back to before I merged in the Alex patch. Redo the Alex patch properly. Then re-merge all the branches that happened after this. Followed by crossing my fingers and running "git prune".

Maybe I'll try all that in a *copy" of my GIT tree first!
-Tony
Next: Linus Torvalds
Message 1 of 3 in “RE: git-whatchanged -p anomoly?”
  1. Luck, TonyAug 18, 2005
  2. Linus TorvaldsAug 18, 2005
  3. Johannes SchindelinAug 18, 2005

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.