Hi Jakub, On Tue, Mar 30, 2010 at 5:10 PM, Jakub Narebski <jnareb@xxxxxxxxx> wrote: > By the way, it would be good to find an example with "evil merge", > which means that the change to given line(s) is in the merge commit > itself. Correctly simplifying history in such case might be > non-trivial. It is a little time consuming to find such a change in the history. I think we can come up some ones at the start of the project manually and put them into the testcases. :) > Another example that it would be good to have is "history split" > example, which means the case where some lines were consolidated > (e.g. after refactoring), and some of lines in "preimage" come > from different lines of history. > > This would help with writing tests for this feature (compare tests > for blame), although they are not in my opinion necessary for the > proposal itself. > > I hope that all this cases would fall naturally from the > implementation. > [...] >> > Push the code somewhere public as you go, even between feature >> > completions. Post RFCs once you have workable features so people can >> > comment. Generally try to be visible. >> > >> > Bonus points if you can think of something visible to do during the >> > period where you look at code, >> >> Yeah, really is a good point. And I have tried to play around on >> github.com and try to set up a http://github.com/byang/my_git for this >> purpose. :) > > my_git is not very descriptive... well, unless you would do your work > on GSoC2010/line-level-history-browser branch, or something like that. > > It might be good idea to have repo.or.cz as an additional repository, > as a fork of git.git repo, and with SoC / GSoC labels. See > http://repo.or.cz/w/git.git/forks?t=soc Ah, a repo at http://github.com/byang/gsoc-line-browser is created and a mirror at http://repo.or.cz/w/gsoc-line-browser.git, I think this is enough. :-) Thanks! Bo -- 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