| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Vik Fearing <vik(at)xocolatl(dot)community>, PostgreSQL WWW <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: Deal with <>s in message IDs |
| Date: | 2014-10-30 18:16:20 |
| Message-ID: | 54528074.6070101@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On 10/30/14, 7:19 AM, Magnus Hagander wrote:
> > I'm not really sure this really belongs in the archives app. We could
> > just have the commitfest app remove them on input.
> >
>
> Oh, now I get it. Yeah, based on that it does sound like the wrong place to fix it. Though if it's easy enough it might be worth doing for convenience. I'll see if there's some place to stick a regexp that can do it safely.
Yes, my original question was if we could basically do the same thing we're doing now to handle /'s. See http://git.postgresql.org/gitweb/?p=pgarchives.git;a=blob;f=django/archives/urls.py;h=d524999dcca8a123b05c294c218d7d93977f4060;hb=HEAD#l28 (line 28) and http://git.postgresql.org/gitweb/?p=pgarchives.git;a=blob;f=django/archives/mailarchives/views.py;h=f6c401a6458ee16050fcd5837a33e848d3cb7644;hb=HEAD#l557 (line 557).
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2014-10-31 05:55:11 | Re: tracking commit timestamps |
| Previous Message | Magnus Hagander | 2014-10-30 12:19:09 | Re: Deal with <>s in message IDs |