Robin, I'm just wondering if the import might be choking on changes happening in parallel branches. If so perhaps passing '--first-parent' to whichever 'git log'-type command you're using to get the ... [More] list of commits might be useful; it will linearize the history and make sure that you don't get any confusing changes. [Less]

Putting RFC822-style e-mail headers in commit messages to have this information is one practice I've seen in at least two places already.

With Free Software, there should be no line drawn between users and developers :-)

Oh, those dreadful, dreadful conversion tools. How dare they test the edge cases of your code. Look, at the end of the day, the repository is simply not corrupted in any way at all, and your ... [More] insistence that this implies some kind of error in the conversion introduced by the conversion tool is categorically wrong. Like I say, this will be obvious to you if you simply read the chapter that describes the object model. If you can point to the source to the importing tool, perhaps I can have a look. [Less]

Yes. Well, the problem here is that this comment simply makes no sense: the source control history is inconsistent. There are probably duplicate commits, or commits that delete code that didn't ... [More] actually get deleted. What does "inconsistent" mean? There are no duplicate commits; they all have unique identifiers (the commit ID). It is possible that there are multiple commits that introduce an identical change; this is called "cherry picking" and are an inevitable consequence of working with branches. That being said, there are multiple enlistments which share history because OHLOH currently only allows tracking of one branch in a given repository. The final part of the comment is a non-sequiter. I am forced to draw the conclusion that your conceptual model of git is deficient. I suggest reading chapter 7 of the user manual which outlines the object model, and consider where in your code the error lies. [Less]

Hi there - the history you are looking at is before Perforce and was manually assembled. I'm afraid I'm really not sure how to comment, because your assertion makes no sense at all. What do you ... [More] think you mean by "multiple file deletions" ? Can you describe what you mean using git commands to show what is going on? And there are no .cs files in that commit; none since about perl 5.0 alpha 9, which is long before the version you refer to. The conversion is still a work in progress, yes - I tried to enlist the (somewhat unfinished) preview repository I made, but the import choked on it. [Less]