From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: New command to check NT's hibernation state
Date: Fri, 02 Dec 2011 07:05:06 +0100 [thread overview]
Message-ID: <4ED86A92.3000506@gmail.com> (raw)
In-Reply-To: <4ED85F41.5070605@gmail.com>
Hello.
On 02.12.2011 06:16, Peter Lustig wrote:
>> Thanks for this. However the coding style isn't according to our
>> standards. Could you adjust to the standard? I recommend looking at
>> other code and reading GNU Coding Standard. E.g. we don't use {0}
>> initialiser, return value of commands, C++ comments or M$-$tyle
>> variables.
>
> Sorry about that. I've reviewed the standard and perused the source
> tree, as you suggested, to determine the best style. Attached is my
> updated file.
>
Much better. There are still few problems like the arbitrary limit (we
avoid any arbitrary limits, you have one easy to avoid on filename
length). Also we don't use such ABORT macros as they offer no
readability advantage. Review in more details when time permits.
> Glad to be of help,
> Peter Lustig
>
> P.S. Do you know if there are any plans in the future to implement
> write operations for filesystems? (I noticed raw disk writing is
> currently supported.) If not, is the reason due to the technical
> challenges (e.g. NTFS only had read-only access in GNU/Linux for quite
> a while) or just a general lack of interest?
Neither. Reliability concerns. Writing to filesystem is potentially
dangerous and needs to be throughly tested. Since writing is rare for
bootloader we won't receive enough testing of these code pathes so every
write will remain a risk. We can't have such risks.
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
next prev parent reply other threads:[~2011-12-02 6:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 5:16 Re: New command to check NT's hibernation state Peter Lustig
2011-12-02 6:05 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-11-04 1:55 Peter Lustig
[not found] <mailman.235.1324573308.26580.grub-devel@gnu.org>
2011-12-23 4:32 ` Peter Lustig
2012-08-12 4:23 ` Peter Lustig
2013-01-28 18:11 ` Vladimir 'φ-coder/phcoder' Serbinenko
[not found] <mailman.171.1324141254.27913.grub-devel@gnu.org>
2011-12-18 3:16 ` Peter Lustig
2011-12-22 12:10 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-04 0:48 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-04 13:13 ` Andrey Borzenkov
2013-11-04 13:24 ` Vladimir 'φ-coder/phcoder' Serbinenko
[not found] <mailman.213.1324054906.20674.grub-devel@gnu.org>
2011-12-17 5:41 ` Peter Lustig
2011-12-17 11:39 ` Vladimir 'φ-coder/phcoder' Serbinenko
[not found] <mailman.207.1322931671.23776.grub-devel@gnu.org>
2011-12-10 6:03 ` Peter Lustig
2011-12-16 15:25 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-12-16 15:30 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-12-03 4:57 Peter Lustig
2011-12-03 10:41 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-27 23:49 Peter Lustig
2011-11-28 1:03 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-28 13:27 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=4ED86A92.3000506@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).