Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > In case revs->limited == 1, the revision walker really reads > everything into revs->commits. The behaviour introduced in > c4025103fa does not behave correctly in that case. > > It used to say: everything which is _still_ in the pipeline > must be a boundary commit. > > So, in the case that revs->limited == 1, filter out all commits > which are not dangling, in effect marking only the dangling > ones as boundary commits. That's what I suggested initially but I think that is wrong. We should show only unshown immediate parents of shown commits at that stage. - 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