Re: [PATCH] Fixed two bugs in git-cvsimport-script.

Junio C Hamano <[EMAIL PROTECTED]> writes: > Junio C Hamano <[EMAIL PROTECTED]> writes: > >> Yes, the patch had some context conflicts with some other patch >> so the patch application was done by hand, and I did a quick and >> dirty cut & paste of the commit message from "cat mbox" output. >> >>

Re: [PATCH] Fixed two bugs in git-cvsimport-script.

Junio C Hamano <[EMAIL PROTECTED]> writes: >> Apparently, my mail was encoded as QP, which is not very popular >> around here. But it seems that the diff part was decoded properly >> before applying. Was that done manually? > > Yes, the patch had some context conflicts with some other patch > so

Re: [PATCH] Fixed two bugs in git-cvsimport-script.

Junio C Hamano <[EMAIL PROTECTED]> writes: > Yes, the patch had some context conflicts with some other patch > so the patch application was done by hand, and I did a quick and > dirty cut & paste of the commit message from "cat mbox" output. > > I will probably drop future patches encoded in QP.

Re: [PATCH] Fixed two bugs in git-cvsimport-script.

> Apparently, my mail was encoded as QP, which is not very popular > around here. But it seems that the diff part was decoded properly > before applying. Was that done manually? Yes, the patch had some context conflicts with some other patch so the patch application was done by hand, and I did a

Re: [PATCH] Fixed two bugs in git-cvsimport-script.

David Kågedal <[EMAIL PROTECTED]> writes: > The git-cvsimport-script had a copule of small bugs that prevented me > from importing a big CVS repository. > > The first was that it didn't handle removed files with a multi-digit > primary revision number. I noticed that this patch was accepted, whic