On Fri, Oct 24, 2014 at 08:37:43AM -0400, JWP wrote:
> My sincere oligopolies to translators, but hwclock is slated for refactoring
> and I expect many message changes will be included. Hopefully, the changes
> will include improving things for translators.
If you really plan to do the refactoring then don't care about
messages at all. The result will be completely different code (I
hope:-). But what we need to to merge all the changes by one pull
request.
Note that the best is to start with date types, try to describe
hwclock by structs (hwclock_control, hwclock_adjtime, hwclock_hwops,
etc.), then write small functions that work with the structs and then
high level logic. See for example cfdisk.c, losetup.c, name.c...
Karel
--
Karel Zak <kzak@xxxxxxxxxx>
http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
