I don't know if git-bisect would help, but I've found it useful to isolate where a particular change took place. You might find that there's a merge that was done in the wrong direction (it happens). Cheers, Alex On Fri, Nov 7, 2014 at 1:14 PM, Scott Elcomb <psema4@gmail.com> wrote:
In a wee bit of a spot :(
Have a git repo with squashed bugs coming back from the dead - and a conference tomorrow where early adopters are supposed to be trained on using the software.
The strange thing is that there doesn't seem to be any indication of corruption or bad merges. There are a few dangling commits, blobs and trees but they don't look to be related.
Not having run into this scenario before I'm not quite sure where to start. Any pointers or suggestions?
Thanks, -- Scott Elcomb @psema4 http://psema4.com/pubkey.txt http://www.pirateparty.ca/
--- GTALUG Talk Mailing List - talk@gtalug.org http://gtalug.org/mailman/listinfo/talk
-- Alex Beamish Toronto, Ontario