On Wed, Oct 31, 2018 at 01:06:56AM +1100, Daniel Axtens wrote:
Migrate our URL schema as follows:Patches: /project/<linkname>/patch/<msgid>/ Cover Letters: /project/<linkname>/cover/<msgid>/ The usual sub-resources (mbox, raw) hang off those URLs. The old style URLs (/patch/NNN/*, /cover/NNN/*) redirect appropriately. Also add /project/<linkname>/comment/<msgid>/ which redirects you in the same way /comment/NNN/ does. Add /message/<msgid> as well. This does not require a project, so if a mail has been sent to multiple projects, the project that you will be redirected to is arbitrary. This patch doesn't expose the new /message/ URL in the UI anywhere, we can address that in a follow-up. I also haven't attempted to do anything meaningful with series. Our database still stores message ids as with angle brackets; we just work around that rather than trying to migrate. That too can come later if we think the pain is justified. Partially-closes: #106 Reported-by: Konstantin Ryabitsev <konstan...@linuxfoundation.org> Reported-by: Linus Torvalds <torva...@linux-foundation.org> Reported-by: Stephen Finucane <step...@that.guru> Signed-off-by: Daniel Axtens <d...@axtens.net> --- v1->v2: Move to msgid by default Add release note Add tests Rebase: rebased on top of master. Tested bundles. I'll apply it in the next couple of days in the absence of objection.
I'm very anxious to see it in place, so please consider me a captive cheerleader.
I'd also be very excited to see a new release with this and the database performance patches included -- perhaps a 2.2? Performance on projects with a long list of paginated patches is still rather slow on MySQL.
Best, -K
signature.asc
Description: PGP signature
_______________________________________________ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
