[PATCHv1 0/3] git-p4: fixing --changes-block-size support · Luke Diamand <hidden> · 2016-06-15
[PATCHv1 1/3] git-p4: additional testing of --changes-block-size · Luke Diamand <hidden> · 2016-06-15
Re: [PATCHv1 1/3] git-p4: additional testing of --changes-block-size · Lex Spoon <hidden> · 2016-06-15
[PATCHv1 3/3] git-p4: fixing --changes-block-size handling · Luke Diamand <hidden> · 2016-06-15
Re: [PATCHv1 3/3] git-p4: fixing --changes-block-size handling · Lex Spoon <hidden> · 2016-06-15
Re: [PATCHv1 3/3] git-p4: fixing --changes-block-size handling · Luke Diamand <hidden> · 2016-06-15
[PATCHv2 0/3] git-p4: fixing --changes-block-size handling · Luke Diamand <hidden> · 2016-06-15
[PATCHv2 1/3] git-p4: additional testing of --changes-block-size · Luke Diamand <hidden> · 2016-06-15
[PATCHv2 2/3] git-p4: test with limited p4 server results · Luke Diamand <hidden> · 2016-06-15
[PATCHv2 3/3] git-p4: fixing --changes-block-size handling · Luke Diamand <hidden> · 2016-06-15
Re: [PATCHv2 3/3] git-p4: fixing --changes-block-size handling · Lex Spoon <hidden> · 2016-06-15
[PATCHv1 2/3] git-p4: test with limited p4 server results · Luke Diamand <hidden> · 2016-06-15
Re: [PATCHv1 2/3] git-p4: test with limited p4 server results · Lex Spoon <hidden> · 2016-06-15
Re: [PATCHv1 0/3] git-p4: fixing --changes-block-size support · Lex Spoon <hidden> · 2016-06-15
Re: [PATCHv1 0/3] git-p4: fixing --changes-block-size support · Luke Diamand <hidden> · 2016-06-15

Re: [PATCHv2 3/3] git-p4: fixing --changes-block-size handling

From: Lex Spoon <hidden>
Date: 2016-06-15 23:05:11

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.

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help