I can forward your comments to them (at coreut...@gnu.org -- the generic comments/development list --, or at bugs-coreut...@gnu.org specifically for bugs), or you can do it yourself. Note that I cannot copy you if I do it -- I do not have your email address; you can email me directly with hggdh2 at ubuntu dot com if you wish that I forward it.
A search on the coreutils mailing list shows many hits on this. For example, http://lists.gnu.org/archive/html/bug- coreutils/2007-01/msg00243.html states: "This is the correct database, but it is not a bug, just an artifact of the screwy way that humans track time. The GNU date documentation is explicit that -1 month operates only on the month field without regards to how many days are in a month, so '31 July -1 month' = '31 June'. But June does not have 31 days, we have to guess whether June 30 or July 1 was intended. No matter which way we guess, someone will complain we guessed wrong. So you are stuck with the current behavior; if all you need is the month changed, then calculate 'July -1 month' independently of the day (and consider a day around the 15th of the month). A similar fuzzy boundary exists around daylight savings boundaries." There are many more hits. An interesting thread is at http://lists.gnu.org/archive/html/bug-coreutils/2010-08/msg00057.html. There is also the FAQ on date: http://www.gnu.org/software/coreutils/faq /coreutils-faq.html#The-date-command-is-not-working-right_002e. Please tell me how you want to proceed. Regards, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/710368 Title: /bin/date --date='next month' is wrong -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
