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

failure doing massive revert

From
MGMike Galbraith <efault@gmx.de>
Date
Sep 18, 2008, 09:09 UTC
Message-ID
<1221728946.8516.14.camel@marge.simson.net>
Greetings,

For reasons I'd rather not go into, I decided to create a merge free tree to try to bisect. I did this yesterday for a smaller range, and it worked fine, and I was able to revert the reverts to re-apply. Trying to revert everything from v2.6.26..today croaked.

for i in `git rev-list --no-merges v2.6.26..HEAD`; do git revert $i < /dev/null; done
Got this far...
Author: Mike Galbraith <efault@gmx.de>  2008-09-18 10:50:58
Committer: Mike Galbraith <efault@gmx.de>  2008-09-18 10:50:58
Parent: 6753354a5984745b0121f7853e4e7a392e25adc7 (Revert "[ARM] 5185/1: Fix spi num_chipselect for lubbock")
Child:  0000000000000000000000000000000000000000 (Local uncommitted changes, not checked in to index)
Branch: master
Follows: v2.6.27-rc6
Precedes: 
    Revert "pktgen: multiqueue etc."
    
    This reverts commit e6fce5b916cd7f7f79b2b3e53ba74bbfc1d7cf8b.

...then began spewing fatal: Dirty index: cannot revert. Probably me being git-ignorant, but figured I'd mention it just in case. I started by whacking all source, followed by checkout -f master, so have no idea what git means by local changes.

	-Mike
Next: Avery Pennarun
Message 1 of 3 in “failure doing massive revert”
  1. Mike GalbraithSep 18, 2008
  2. Avery PennarunSep 18, 2008
  3. Mike GalbraithSep 19, 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.