I don't have a patch history; hwclock has not been a big enough project to warrant such code control process. And I don't know any other practical way to break down the difference between the two hwclocks into logical patches. And I'm really not inclined to re-implement stuff -- that would be tedious for me. Looking over the util-linux-ng mailing list, I see a bunch of stuff I did once before, but not so that I could turn it into a patch today. So maybe there's nothing mergeable after all. Or I'm just not the right guy to do it. I'm pretty aggressive about changing code, and I can tell that's not the util-linux-ng temperament. Do you think there's any way to ship a stable and advanced version, where the advanced version might some day have enough exposure that you'd consider it stable? Even some of the things you're considering adding are kind of fringy, and it would be better to have a place to put those where they wouldn't bother people who won't use them. -- Bryan Henderson San Jose, California -- To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
