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

2023-04-03 Thread Thomas Schmitt
Hi, i asked how to delete the local branch after deleting the remote one. The helpful internet told me to try git branch -d api-doc which did what i want. So i deleted more branches: trackno-higher-one pete_batard_gcc_warnings pete_batard_ce_v3 ts-multiextent pragmatic-multiextent By

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

2023-04-03 Thread Thomas Schmitt
Hi, when trying to switch from branch "joliet_multi_extent" to "master" i was notified that a message text change did not make it into git. So i committed ab3ad52 Remove blanks from the test names in check_multiextent and pushed "joliet_multi_extent" again. Sorry for the confsion. Have a nice

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

2023-04-03 Thread Thomas Schmitt
Hi, Rocky Bernstein wrote: > Over the weekend I removed my stale branches from libcdio's git. I partly failed to do the same with a first deletion candidate. My cheat sheet says: git push origin --delete $branch_name When i do git push origin --delete api-doc i get the reply To scdbac.

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

2023-04-03 Thread Thomas Schmitt
Hi, i pushed again branch "joliet_multi_extent" for review. The new commit re-introduces the old multi-extent test ISO as test/data/multi_extent_8k_emul_toc_padded.iso and a file test/README.multiextent which explains the differences between the now three multi-extent ISOs. I also solved the

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

2023-04-03 Thread Rocky Bernstein
On Mon, Apr 3, 2023 at 5:31 AM Thomas Schmitt wrote: > Hi, > > Rocky Bernstein wrote: > > if xoriso or some other burner program in the past created ISO 9660 > images > > in a particular way, > > xorriso still produces the larger ISOs by default. Normally it does not > matter to have 300+ KiB of

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

2023-04-03 Thread Thomas Schmitt
Hi, Rocky Bernstein wrote: > if xoriso or some other burner program in the past created ISO 9660 images > in a particular way, xorriso still produces the larger ISOs by default. Normally it does not matter to have 300+ KiB of waste, while the advantage is safety against the Linux TAO CD bug and t

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

2023-04-03 Thread Rocky Bernstein
Over the weekend I removed my stale branches from libcdio's git. On Fri, Mar 31, 2023 at 5:25 PM Thomas Schmitt wrote: > 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

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