{"thread":{"id":"1780","subject":"replaying commits against CVS","startedAt":"2005-09-12T06:56:42Z","lastAt":"2005-09-12T06:56:42Z","messageCount":1,"participants":["Martin Langhoff"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"8365","messageId":"46a038f905091123564b663062@mail.gmail.com","threadId":"1780","inReplyTo":null,"subject":"replaying commits against CVS","fromName":"Martin Langhoff","fromEmail":"martin.langhoff@gmail.com","sentAt":"2005-09-12T06:56:42Z","receivedAt":"2005-09-12T06:56:42Z","isPatch":false,"sender":{"key":"martin.langhoff@gmail.com","avatar":"https://gravatar.com/avatar/1e3f311b6c4c15836501901ca58f8c0b0667246488084ba524d8bc9867e22fd9?d=mp&s=160"},"body":"I am not looking for a full-blown 2 way gateway. But we do work quite\na bit on some projects where the upstream is using CVS, and it'd be\ngreat to be able to replay our history against CVS. (And thus, when\nthe commits are echoed back, git-cherry will do the right thing and\nskip them).\n\nMy current plan is to take git-apply-mbox and transform it to perform\nthe nasty deed. But smarter people have been merging mbox-formatted\npatches automatically for ages, and perhaps there's a script out there\nthat is known to work reliably.\n\ncheers,\n\n\nmartin\n"}]}