From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: [PATCH 2/6] Fix common misspellings in drivers
Date: Tue, 14 Sep 2010 16:02:45 +0900 [thread overview]
Message-ID: <1284447765.2405.51.camel@localhost.localdomain> (raw)
In-Reply-To: <AANLkTim_dpW=WF-s0oJmFd9E1dMwT43sypkMRrjMP9N-@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 657 bytes --]
Hi Aki,
> >> - * Copyright (C) 2010 Nokia Corporation and/or its subsidary(-ies).
> >> + * Copyright (C) 2010 Nokia Corporation and/or its subsidiary(-ies).
> >
> > for these kind of changes, I prefer if you have buy in from the Nokia
> > guys. Some companies have strict rules on the copyright header. I know
> > that with Intel we try to follow them consistently for all projects. So
> > if Nokia wants to "misspell" this, then that is fine with me actually.
>
> This is a real misspelling; in other places in the source tree it is
> spelled correctly.
fair enough. And all of the patches have been pushed now.
Regards
Marcel
next prev parent reply other threads:[~2010-09-14 7:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 1:32 [PATCH] Fix common misspellings Lucas De Marchi
2010-09-14 1:35 ` Marcel Holtmann
2010-09-14 2:32 ` Lucas De Marchi
2010-09-14 2:37 ` Denis Kenzior
2010-09-14 3:06 ` [PATCH 1/6] Fix common misspellings in documentation Lucas De Marchi
2010-09-14 3:06 ` [PATCH 2/6] Fix common misspellings in drivers Lucas De Marchi
2010-09-14 5:08 ` Marcel Holtmann
2010-09-14 6:51 ` Aki Niemi
2010-09-14 7:02 ` Marcel Holtmann [this message]
2010-09-14 3:06 ` [PATCH 3/6] Fix common misspellings in gatchat Lucas De Marchi
2010-09-14 3:06 ` [PATCH 4/6] Fix common misspelling in gisi Lucas De Marchi
2010-09-14 3:06 ` [PATCH 5/6] Fix common misspellings in TODO file Lucas De Marchi
2010-09-14 3:06 ` [PATCH 6/6] Fix common misspelling in source files Lucas De Marchi
2010-09-14 3:21 ` [PATCH] Fix common misspellings Gu, Yang
2010-09-14 22:36 ` Lucas De Marchi
2010-09-15 5:26 ` Gu, Yang
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=1284447765.2405.51.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=ofono@ofono.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