Martin Langhoff <martin <at> catalyst.net.nz> writes: > I just don't worry about the timestamps > > I normally track the Moodle CVS tree, and do all my "new feature" and > "client customization" branches in git. The feature branches I rebase > aggressively, until they are ready to be "landed" in CVS. It is in that > "landing in cvs" that I use cvsexportcommit, usually with a long list of > commits! How do you get git-cvsimport to avoid the "duplicate" commit that it creates when it imports a commit that you "landed" in CVS with git-cvsexportcommit? I call this commit a duplicate because though it has a different SHA1 identifier, commit timestamp, and even committer email address, it refers to the same tree identifier as the landed commit. However, because it has the same textual difference as the landed commit, the duplicate commit introduces no new textual difference. It is essentially an "empty" commit. Do you just accept and ignore this empty commit? Derek - 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
