On Tue, 2016-01-19 at 12:20 -0500, Konstantin Ryabitsev wrote: > Hi, all: > > I have a slightly off-topic question -- one of our projects requires > that all patches sent via a mailing list are archived on a public > website (just specifically patches, not any other discussions). > Before we set up patchwork with no project admins (basically) -- is > there any other tools you may be aware of that are able to receive > mailing list traffic and create a static archive of any patches seen?
lkml.org has something similar, I think - at least it tries to identify patches? One caveat with using patchwork for this, perhaps: in my experience, patchwork sometimes (though really rarely) drops patches, I think due to unexpected encodings. So if patchwork isn't part of the patch application process, not all patches that get applied might actually be archived in patchwork. johannes _______________________________________________ Patchwork mailing list [email protected] https://lists.ozlabs.org/listinfo/patchwork
