Ah - that explains it. I added additional files to the series, but simply re-applied the original round of patches. They would've not been tagged as v4, while the patches pertaining to the newly-modified files had v4 in the subject.
I'll be more thorough in future patch revisions. Thanks for the explanation. -- Mike Shuey On Sat, May 23, 2015 at 8:39 AM, Sudip Mukherjee <sudipm.mukher...@gmail.com> wrote: > On Sat, May 23, 2015 at 08:09:54AM -0400, Michael Shuey wrote: >> BTW, you keep mentioning a v5 that I sent. Where is that, exactly? >> The last round of patches I sent I've kept labeled as "PATCH v4", and >> I only hit git send-email once. Could you forward me something from >> this v5 series, so I could see if anything is amiss on my end? > > I think it was not a v5. But what happened is in your series some > of the patches were marked as v4 and some were not having any version > so it appeared like a fresh series again. Like 1/13,2/13,3/13 has v4 > but the others donot have a version. > > regards > sudip -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
