It's wrong in the sense that not the obvious result users expect. But it's 100% technically right. It's always tough to deal with this kind of situation. Do yo

It's wrong in the sense that not the obvious result users expect. But it's 100% technically right. It's always tough to deal with this kind of situation. Do you document it all over the place and hope users read it? Do you parse the command when it's first created and warn the user that %g is different than %Y? Do you just ignore the issue and deal with the small number of emails at the beginning of every year? I think a combination of docs + automated checks is best depending on the circumstances.