libburnia/legacy
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Updated change log and web page

Browse Source
This commit is contained in:
Thomas Schmitt 2013-05-16 13:11:16 +00:00
parent 47bf33ef53
commit 47132b6b41
2 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
libisoburn/trunk/ChangeLog
View File

@ -4,6 +4,7 @@ SVN trunk (to become libisoburn-1.3.0.tar.gz or higher)
directories. directories.
* Bug fix: -as mkisofs -print-size failed with -isohybrid-mbr and a single * Bug fix: -as mkisofs -print-size failed with -isohybrid-mbr and a single
boot image. Regression introduced by libisoburn-1.2.8. boot image. Regression introduced by libisoburn-1.2.8.
* Bug fix: -as mkisofs -path-list did not switch to --no-emul-toc by default.
* Bug fix: Unspecified Expiration Time and Effective Time of ISO volume was * Bug fix: Unspecified Expiration Time and Effective Time of ISO volume was
represented by 0-bytes rather than ASCII '0' digits. represented by 0-bytes rather than ASCII '0' digits.
* Bug fix: Reserved and unused fields of APM entries were not zeroed. * Bug fix: Reserved and unused fields of APM entries were not zeroed.

7
libisoburn/trunk/xorriso/xorriso_eng.html
View File

@ -652,10 +652,13 @@ cdrecord and mkisofs.</DT>
<DT><H3>Development snapshot, version 1.2.9 :</H3></DT> <DT><H3>Development snapshot, version 1.2.9 :</H3></DT>
<DD>Bug fixes towards xorriso-1.2.8: <DD>Bug fixes towards xorriso-1.2.8:
<UL> <UL>
<LI>Disk paths with components '.' or '..' could be mistaken for directories <LI>Disk paths with components '.' or '..' could be mistaken for directories.
</LI> </LI>
<LI> <LI>
-as mkisofs -print-size failed with -isohybrid-mbr and a single boot image -as mkisofs -print-size failed with -isohybrid-mbr and a single boot image.
</LI>
<LI>
-as mkisofs -path-list did not switch to --no-emul-toc by default.
</LI> </LI>
<LI>Reserved and unused fields of APM entries were not zeroed.</LI> <LI>Reserved and unused fields of APM entries were not zeroed.</LI>
<LI> <LI>