Re: [Libcdio-devel] About old branches of mine

2023-03-31 Thread Thomas Schmitt
Hi, Rocky Bernstein > test/data/multi_extent_8k.iso| Bin 524288 -> 122880 bytes > I think both versions should be there. We should be testing not just how > things are created currently, but also how they may have been created in > the past. I realize that i forgot to take into accoun

Re: [Libcdio-devel] About old branches of mine

2023-03-31 Thread Rocky Bernstein
I just pulled master and see: test/data/multi_extent_8k.iso| Bin 524288 -> 122880 bytes I think both versions should be there. We should be testing not just how things are created currently, but also how they may have been created in the past. On Fri, Mar 31, 2023 at 4:22 AM Thomas

[Libcdio-devel] About old branches of mine

2023-03-31 Thread Thomas Schmitt
Hi, please ignore my previous mail with the same subject. I pasted the wrong mail body by mistake. Meant was this: I see some now obsolete branches of mine. Merged according to https://git.savannah.gnu.org/cgit/libcdio.git/log/ are: pete_batard_ce_v34 days pete_batard_gcc_warnin

[Libcdio-devel] About old branches of mine

2023-03-31 Thread Thomas Schmitt
Hi, i now merged "joliet_multi_extent" by git merge cb03533aaba6113465b19157577e631e26406c7e and pushed it after a final "make check". I wonder, though, why check_multiextent.sh is not mentioned in the "make check" output. I see it in the check_SCRIPTS definition of test/Makefile.am where it

Re: [Libcdio-devel] Can we merge branch "joliet_multi_extent" ?

2023-03-31 Thread Thomas Schmitt
Hi, i now merged "joliet_multi_extent" by git merge cb03533aaba6113465b19157577e631e26406c7e and pushed it after a final "make check". I wonder, though, why check_multiextent.sh is not mentioned in the "make check" output. I see it in the check_SCRIPTS definition of test/Makefile.am where it