Nicolas Pitre <nico@xxxxxxx> wrote: > I think you should call it something else than rfc2822. Because > parse_date() accepts much more than just rfc2822. What about "cooked"? It does accept a lot more than that, but straying away from rfc2822 gets into the grey areas of parse_date(). E.g. it matches crap such as 'yyyy-mm-dd' or 'yyyy-dd-mm'. But that is completely ambiguous! I don't really want to advertise that it is accepting non-RFC 2822 input here. I was thinking of doing an `iso` (yyyy-mm-dd hh:mm:ss) format, which may just defer into parse_date(), but again encourage the frontend to *only* feed that ISO style format. -- Shawn. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html