larsxschnei...@gmail.com writes: > From: Lars Schneider <larsxschnei...@gmail.com> > > diff to v6: > * Always print the encoded path in verbose mode. > > v6 is already on next (a9e383). This patch must be applied on next. > Is this the right way to handle this situation?
Yes, I thought that the reviewers found v6 was solid enough, and it is now in 'next'. It is best to do further polishing on the tip of the topic that is in 'next', i.e. a9e38359 (git-p4: add config git-p4.pathEncoding, 2015-09-03). Labeling the patch as v7 is misleading, but from the context (like your cover letter description) it was clear that the patch is a follow-up, so everything looks good from procedural point of view. Thanks for making reviewer's life easier. -- 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
