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
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
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
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
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.
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
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
Hi,
one of the unclear branches seems not to have made it into "master":
ts-cdtext-fix
I don't see traces of its commits (listed from oldest to newest):
6347ef09b6d1a6211b93425bd9b12b9d92b34e8c
Added comment to explain why function language_code_tests() exists
bde2647b444136e2d23d303d
Hi,
it looks like the two commits
bde2647b444136e2d23d303d0a02d27383fcea32
6347ef09b6d1a6211b93425bd9b12b9d92b34e8c
were overridden by newer changes.
git merge bde2647b444136e2d23d303d0a02d27383fcea32
replied
Already up-to-date.
Closer inspection of the code shows that the removal of tra
If there are not that many changes, it might be simpler just to start a new
branch and add the changes you want there from the one where you are having
a problem.
On Mon, Apr 3, 2023 at 11:42 AM Thomas Schmitt wrote:
> Hi,
>
> it looks like the two commits
> bde2647b444136e2d23d303d0a02d27383f
Hi,
Rocky Bernstein wrote:
> If there are not that many changes, it might be simpler just to start a new
> branch and add the changes you want there from the one where you are having
> a problem.
It's just one word to change. So i will wait until the decisions about
the two pending branches are m
11 matches
Mail list logo
