Collin Funk wrote: > These two TODO entries were pretty simple. One of the ChangeLog > entries listed to a test case Bruno wrote that worked for testing both > of them. > > [collin@debian gnulib]$ gnulib-tool.py --create-testdir --dir=testdir-all > --single-configure > module parse-datetime2 depends on a module with an incompatible license: > gettime > module parse-datetime2 depends on a module with an incompatible license: > nstrftime > module parse-datetime2 depends on a module with an incompatible license: > parse-datetime > module parse-datetime2 depends on a module with an incompatible license: > time_rz > module parse-datetime2 depends on a module with an incompatible license: > timespec > module parse-datetime2 depends on a module with an incompatible license: tzset > module ucs4-utf16 depends on a module with an incompatible license: > unistr/u16-uctomb > module utf16-ucs4 depends on a module with an incompatible license: > unistr/u16-mbtouc > module utf16-ucs4-unsafe depends on a module with an incompatible license: > unistr/u16-mbtouc-unsafe > > The first patch fixes the parse-datetime2 warnings in the same way > that gnulib-tool does (ready for the release of parse-datetime3). The > second fixes the libunistring ones. Let me know if I missed anything.
Thanks! Applied both patches. Bruno