> This is the second iteration on the models and mail parsing the series > aware > patchwork. > > Since the first iteration, the main big addition is some handling of new > versions of patches and series after the initial submission and review > comments. All revisions of the same series are aggregated into the same top > level "Series" object. More details in the actual commit messages. > > It's also a good time to start documenting what patchwork understands. If > you > are reading this and your project uses a wildly different way to send > v2/v3/.. > patches after review, please do speak up. > > http://patchwork.readthedocs.org/en/freedesktop.org/manual.html > > I'm fixed a number of bugs compared to the initial submission, tightened a > bit > the schema constraints as well to catch errors early. Note that the code > actually parses a larger number of cases that the ones discussed in the > documentation page above. > > I'm fully expecting this doesn't handle some cases we'd like to support, > but > works on a reasonable amount of mails I use for testing (~10,000 mails from > the > intel-gfx mailing-list). I also know some cases that aren't supported and > that > I don't intend to support unless there is some demand. For instance, > resending > a full v2 series as a reply of the v1 cover letter doesn't work and, while > I > have seen that occurence happen on intel-gfx, it's usually new contributors > that don't quite know how we'd like v2 of series to be sent (because it's > not > really well clear/documented).
I've replied to all the patches available bar one (which I want to investigate a little further). However, I'm missing two patches. Can you submit these separately or resend the series (ideally after addressing comments)? Stephen _______________________________________________ Patchwork mailing list [email protected] https://lists.ozlabs.org/listinfo/patchwork
