Unless I am reading something wrong, the "new_changes" variable could be dropped now. It was needed for the -m version for detecting the smallest change number that was returned. Otherwise it looks good to me. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
- [PATCHv1 2/3] git-p4: test with limited p4 server results Luke Diamand
- [PATCHv1 3/3] git-p4: fixing --changes-block-size handling Luke Diamand
- Re: [PATCHv1 3/3] git-p4: fixing --changes-block-size ... Lex Spoon
- Re: [PATCHv1 3/3] git-p4: fixing --changes-block-s... Luke Diamand
- [PATCHv2 0/3] git-p4: fixing --changes-block-s... Luke Diamand
- [PATCHv2 2/3] git-p4: test with limited p4... Luke Diamand
- [PATCHv2 1/3] git-p4: additional testing o... Luke Diamand
- [PATCHv2 3/3] git-p4: fixing --changes-blo... Luke Diamand
- Re: [PATCHv2 3/3] git-p4: fixing --ch... Lex Spoon
- Re: [PATCHv2 3/3] git-p4: fixing ... Junio C Hamano
- Re: [PATCHv2 3/3] git-p4: fixing ... Lex Spoon
- Re: [PATCHv2 3/3] git-p4: fixing ... Junio C Hamano
- Re: [PATCHv1 0/3] git-p4: fixing --changes-block-size suppo... Lex Spoon