From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: OCFS2 support
Date: Fri, 04 Nov 2005 00:43:08 +0100 [thread overview]
Message-ID: <87fyqdxppv.fsf@student.han.nl> (raw)
In-Reply-To: <20051103231920.GB28731@ca-server1.us.oracle.com> (Mark Fasheh's message of "Thu, 3 Nov 2005 15:19:20 -0800")
Mark Fasheh <mark.fasheh@oracle.com> writes:
> Hi,
> On Thu, Nov 03, 2005 at 11:42:40PM +0100, Marco Gerards wrote:
>> A consistent coding style is quite important for us. Would it be a
>> problem for you to have a look at the GCS and make the required
>> changes to your code? If you need any help, pointers, etc. I am more
>> than willing to help.
> Yeah no problem at all. If you don't mind, it'd help alot if you could point
> out the problems - I thought I was being very thorough but clearly I was
> wrong :)
>
> Basically with respect to coding style I copied what I saw in ext2.c /
> xfs.c. Also, I set the emacs c-style to 'gnu'.
>
> Maybe there's a .indent file or something I could run it through?
I think GNU indent defaults to the GCS. The GCS is a bit more than
just indentation, for example it also says stuff about naming
variables, the maximum line lengths, how comments are formatted, etc.
>> A more important issue is the copyright. For GRUB 2 all copyrights
>> are assigned to the FSF. Would it be possible to do this for your
>> code as well? I assume it would mean Oracle has to agree with this.
> I suspect this will be ok - my boss is contacting our legal department to
> make sure.
Cool.
--
Marco
next prev parent reply other threads:[~2005-11-03 23:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 22:15 OCFS2 support Mark Fasheh
2005-11-03 22:42 ` Marco Gerards
2005-11-03 23:19 ` Mark Fasheh
2005-11-03 23:43 ` Marco Gerards [this message]
2005-11-04 1:13 ` Mark Fasheh
2005-11-04 1:17 ` Mark Fasheh
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=87fyqdxppv.fsf@student.han.nl \
--to=metgerards@student.han.nl \
--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.