Your message dated Fri, 13 Nov 2015 00:32:56 +0100 with message-id <[email protected]> and subject line Re: hwclock.sh: use date --rfc-2822 has caused the Debian Bug report #321862, regarding hwclock.sh: use date --rfc-2822 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 321862: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=321862 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: util-linux Version: 2.12p-4 Severity: wishlist File: /etc/init.d/hwclock.sh Don't say echo "System Clock set. Local time: `date`" say echo "System Clock set. Local time: `date --rfc-2822`" as $ date Mon Aug 8 04:09:16 CST 2005 CST could be several places in the world, while $ date --rfc-2822 Mon, 08 Aug 2005 04:09:26 +0800 is explicit.
--- End Message ---
--- Begin Message ---Hello Dan Jacobson. Thanks for your bug report and sorry for the decade late reply. On Mon, Aug 08, 2005 at 04:11:33AM +0800, Dan Jacobson wrote: > Package: util-linux > Version: 2.12p-4 > Severity: wishlist > File: /etc/init.d/hwclock.sh > > Don't say > echo "System Clock set. Local time: `date`" > say > echo "System Clock set. Local time: `date --rfc-2822`" > as > $ date > Mon Aug 8 04:09:16 CST 2005 > CST could be several places in the world, while > $ date --rfc-2822 > Mon, 08 Aug 2005 04:09:26 +0800 > is explicit. I disagree. The rfc2822 format does not include any additional information, it is just more human-unfriendly. The main difference is that instead of using the standard CST (Central Standard Time) name it uses the UTC offset.... I might have agreed with your point if the main idea was to make the output more easily machine parseable, which I can't see that it is intended in this particular case. I've just tagged the bug as 'wontfix' accordingly. Now closing this bug report to avoid cluttering up the backlog. Please adjust queries for 'wontfix' bugs to include both open and closed bugs. Regards, Andreas Henriksson
--- End Message ---
