On Sun, Mar 23, 2008 at 3:28 PM, Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: > I think you will have to go to the line level to achieve what Junio > suggested. I'm not sure what you mean with "go to the line level"? Do you mean that using a Graph is not possible? > Timezones are recorded as epoch (seconds since Jan 1, 1970) and timezone. > So yes, you have that, _provided_ you trust the users to set up that thing > correctly. Yeah, I'll trust the user on this ;). If the timezone is stored as well this should be easy to do, sweet. > > > * Identify "buggy commits" from history, without testing. Zeroth order > > > > A feature like this would fit well with the other "buggy > > commit/maintainer detection" but would require a lot of customization. > > However, considering git already comes with a good customization > > system it should still be feasible. > > Yes. And it would be really interesting for me. Until it shows that I am > the biggest offender, of course. Maybe we can put in an if-check for user "Johannes Schindelin"? ;) > I think the bigger problem is not visualising it, but finding what is > buggy, and what not. Yes, ofcourse, I think I'll be busy mostly following lines across commits and after that determining if a commit is buggy or not. > I think it can be vague about the order in which things will be > implemented. And the features which you think might be too complicated > should be marked as such: "possible extension (which might not be finished > within this project): <blabla>". Cool, I think I can start on a RC for my application then! (Maybe I should'of tracked it with git, then I could tag it...) Thanks for the feedback, I really want to come up with a superb application! Sverre -- 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
