From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [patch] GRUB possible patches
Date: Sat, 20 Feb 2010 12:03:40 +0100 [thread overview]
Message-ID: <4B7FC18C.7020103@gmail.com> (raw)
In-Reply-To: <29547223.11266392506886.JavaMail.root@wombat>
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
gburanov@gmail.com wrote:
>> First part applied
>>
> Thanks!
>
>
>> Please don't put unrelated patches into single file. Fast look on the
>> joliet.c of mkisofs suggests that it's not the case for its joliet. It
>> seems there is more to it. Can you find some normative documents?
>>
>
> I searched a bit and found the following information:
> Doc: http://www.transelectro.ru/technology/standard/joliet_spec.htm
> In the documentation:
>
> "Simply put, SEPARATOR 1 and SEPARATOR 2 shall be expanded to 16-bits".
>
> SEPARATOR 2 is ';' - which is used signify the version number of a file.
>
> About mkisofs - it seems it's just their implementation of joilet, they can use or not use versioning
> See this topic
> http://www.mail-archive.com/cdwrite@other.debian.org/msg03199.html
>
>
Ok, I agree that it should be fixed but I made and applied a slightly
different fix
>> We use only C-style comments
>>
> Ok, I will create new patch soon
>
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]
prev parent reply other threads:[~2010-02-20 11:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 13:00 [patch] GRUB possible patches George Buranov
2010-02-11 15:44 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-02-12 14:20 ` gburanov
2010-02-16 12:13 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-02-17 7:41 ` gburanov
2010-02-20 11:03 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B7FC18C.7020103@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.