-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Linus Torvalds wrote: > > On Mon, 9 Jul 2007, VMiklos wrote: >>> I think bk can export to CVS and then git can import from CVS. >> i think so > > That's how I did my kernel history, and cvsps has a special "BK mode", > which knows to trust the CVS timestamps more when importing from a BK CVS > archive (since the timestamps will then be exact). > > That said, the quality of the result isn't stellar. The CVS export will > obviously linearize the BK information, so you do lose things. So there's > actually a better kernel BK->git archive around which doesn't do that, but > that was done apparently from a custom database, so it's not reproducible. > > Linus > - We have a CVS repository that we want to import into bitkeeper. I tried the bk import option, including with a branch bug fix, but it's still having problems. I imported the CVS repository to git and it worked great. Since all of our other repository are in bitkeeper the management would like to stick with CVS. With git apparently still being weak in the area of supporting difftool on different version that seems somewhat reasonable for the time being. The folks at bitmover are converting you kernels to bk and it's maintaining the branch history and I'd like to do the same. So far they haven't help us convert the git repository to bk. Do you happen to know of someone else that might now how to do this in case the folks at bitmover can't provide the scripts to convert this git repository to bk? I was curious why the difftool paradigm hasn't been integrated into the git GUIs. It's very comfortable and I think it has been used in other source code control systems, for example Sun Microsystems. - -piet -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHE/pKJICwm/rv3hoRAs/QAJoDL0HQDaOAI1x6UakEiVvti9tI2wCfUpGI bfyKH+ykUK7p2AL9CSE+XXc= =0gnp -----END PGP SIGNATURE----- - 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
