On Wed, 2 July 2008, Stephen R. van den Berg wrote: > Jakub Narebski wrote: >> >> [...] So I think that it would >> be better to provide generic git-filter-branch filter which can >> understand this "generalized grafts" file format, or rather >> 'description of changes' file. Put it in contrib/, and here you >> go... > > The problem is that the process of fixing history is an iterative one, > which can take many months, and everytime you make a change, the > correctness needs to be viewed using gitk. [...] I wanted to propose that git-filter-branch generic "generalized grafts" file based filter should be accompanied by extending gitk so it understand this format to... ...but after reading wonderfull suggestion to create new commits with corrected contents, and insert them (replace older version by them) using grafts, thought and brought independently by Dmitry Potapov and Petr Baudis, I think that you would be best with extending gitk to support this way instead. You would have to extend gitk to maintain reverse revision mapping (from revision to its children), and then you would be able to edit history interactively from within gitk, with gitk correcting its internal structures to redisplay changed commits, and creating commits and doing grafting behind the scenes for later git-filter-branch run. -- Jakub Narebski Poland -- 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
