On Thursday 19 December 2019 09:30:30 Rafał Miłecki wrote:
> On Wed, 18 Dec 2019 at 12:44, Pali Rohár wrote:
> >
> > On Tuesday 17 December 2019 08:28:35 Rafał Miłecki wrote:
> > > From: Pali Rohár
> > >
> > > commit e526f503918cc29d8b1ccf36a5c3a34645d2be6e upstream.
> > >
> > > When FAT
On Wed, 18 Dec 2019 at 12:44, Pali Rohár wrote:
>
> On Tuesday 17 December 2019 08:28:35 Rafał Miłecki wrote:
> > From: Pali Rohár
> >
> > commit e526f503918cc29d8b1ccf36a5c3a34645d2be6e upstream.
> >
> > When FAT directory entry has leading byte 0x05 it is interpreted as byte
> > 0xE5. This is
On Tuesday 17 December 2019 08:28:35 Rafał Miłecki wrote:
> From: Pali Rohár
>
> commit e526f503918cc29d8b1ccf36a5c3a34645d2be6e upstream.
>
> When FAT directory entry has leading byte 0x05 it is interpreted as byte
> 0xE5. This is how FAT stores file name which starts with byte 0xE5 as
>
On December 17, 2019 7:28:35 AM UTC, "Rafał Miłecki" wrote:
>From: Pali Rohár
>
>commit e526f503918cc29d8b1ccf36a5c3a34645d2be6e upstream.
>
>When FAT directory entry has leading byte 0x05 it is interpreted as
>byte
>0xE5. This is how FAT stores file name which starts with byte 0xE5 as
>leading
From: Pali Rohár
commit e526f503918cc29d8b1ccf36a5c3a34645d2be6e upstream.
When FAT directory entry has leading byte 0x05 it is interpreted as byte
0xE5. This is how FAT stores file name which starts with byte 0xE5 as
leading byte in 0xE5 in FAT directory entry means that file slot is empty.
