Re: git-cvsexportcommit and commit date

söndagen den 10 februari 2008 skrev Derek Mahar:

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?

git rebase will drop those "empty" commits by default and you'll end up with the
cvs-imported version.

-- robin