Hi,
I think this has come up before [1],[2] but we ran into this at $dayjob today.
Our default MUA has an annoying habit of using a non RFC822 date format when
saving an email as plaintext. This means the first 12 days of every month we
run into the ambiguous date problem (our date convention is
Chris Packham judge.pack...@gmail.com writes:
Our default MUA has an annoying habit of using a non RFC822 date format when
saving an email as plaintext. This means the first 12 days of every month we
run into the ambiguous date problem (our date convention is dd/mm/yy).
I see code in date.c
On 09/12/2012 09:48 PM, Junio C Hamano wrote:
Chris Packham judge.pack...@gmail.com writes:
Our default MUA has an annoying habit of using a non RFC822 date format when
saving an email as plaintext. This means the first 12 days of every month we
run into the ambiguous date problem (our date
Chris Packham judge.pack...@gmail.com writes:
Consistent as long as you save as the default .txt. Some people have
trained themselves to use the save as .eml option which uses RFC822
style output.
Yuck.
Could this be done in a applypatch-msg
hook?
Isn't the hook about fixing up the log
4 matches
Mail list logo
