[PATCH] Updated openat test

[Katerina Koukiou]

I think the Linux kernel coding style
<https://www.kernel.org/doc/Documentation/CodingStyle>  is fine for someone
like me, new to writing patches. I could adjust it, to meet the projects
specific requirements, for example by removing the kernel specific parts.
Do you think this is ok, or should the Documentation be written from
scratch?
Katerina Koukiou

On Thu, Mar 24, 2016 at 2:11 PM, Philippe Ombredanne <pombredanne at nexb.com>
wrote:

> On Thu, Mar 24, 2016 at 12:51 PM, Katerina Koukiou
> <k.koukiou at googlemail.com> wrote:
> > I changed the test again as suggested.
> > Is there a document that I can read to understand the identation rules
> for this project? Or just by observing the other's code?
>
> There is no such doc, the way to go is observing the code and Dmitry
> has the final say.
>
> > I had not observed the identation for the includes for example, because
> it differs between authors.
>
> Good point!
> Now based on Dmitry's feedback you could write the doc and submit a
> patch with the doc for it to include in README-hacking ?
> That would be a nice small subtask as part of a GSOC project
> --
> Cordially
> Philippe Ombredanne
>
>
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
> _______________________________________________
> Strace-devel mailing list
> Strace-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/strace-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.strace.io/pipermail/strace-devel/attachments/20160324/fdf8bb8c/attachment.html>