failure doing massive revert

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxx>  2008-09-18 10:50:58
Committer: Mike Galbraith <efault@xxxxxx>  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

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux