Not per se, but it does allow bored students to see "what once was", or generate visual change graphs. Just think of, say, Wine, which managed to import all their version control history from CVS into SVN, and I think now into Git as well. You can easily go back and see what Wine looked like back in 1994, if you're ever curious. On Feb 5, 2012, at 2:22 PM, Jody wrote: > I just pushed the code to Git. I don't know much about CVS and I have always personally hated it since I got on SourceForge 11 years ago. I just wanted to get the code in an easily reachable place as quickly as I could, so that's what I've done. Do we need the CVS history, moving forward? > > On 2/5/2012 2:18 PM, Kirn Gill wrote: >> >> That's one better than I had planned. I was just going to push the changes to CVS and call it a day. Say, did you import all the CVS history into git or just a checkout of the latest sources + the patches? >> >> > -- > To unsubscribe from this list: send the line "unsubscribe linux-8086" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-8086" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
