Volker Kuhlmann <list0570@xxxxxxxxxxxxxxx> writes: >> But I'm not sure why 13? > > It's the minimum that is absolutely required to cover the DST offset in > New Zealand. At the moment. There may be other places around the date > line for which even that is not sufficient. Someone's been thoughtless > already (has happened regularly for decades, probably won't be the last > time either). Fix it properly. > > If the kernel uses +-24 in places then please stick to +-24. There may > be a reason for that not everyone knows about. The purpose of the range > check is to be a SANITY check, not to tell me, the user, how I have to > operate my system. If I want 3 minutes, I want 3 minutes, and it's not > the kernel programmer's job to enforce. > > Or do you wish to track the legal time zone AND DST offsets in every > place in the world, make a list, stick that into the kernel, and > maintain it? I hope not. Actually, it is correct timezone support (for example, daylight). > A good limit would be 2 less of whatever fits into 8 bit. Or something > like that. Like +-120. I'm not against to change. But don't want to change this multiple times, and step by step. It is why I'm asking. Well so, how does it overs 24 hours (i.e. a day) for sane tz offset (implementation is just a dumb adjustment of timestamp, but this option should means tz offset)? (And +-24 hours is used for TZ spec too.) Thanks. -- OGAWA Hirofumi <hirofumi@xxxxxxxxxxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
