From: Marcel Holtmann <marcel@holtmann.org>
To: Ron Shaffer <rshaffer@codeaurora.org>
Cc: Inga Stotland <ingas@codeaurora.org>,
linux-bluetooth@vger.kernel.org, johan.hedberg@gmail.com
Subject: Re: [PATCH 1/3] Support for adding UUID128 to extended inquiry response
Date: Fri, 09 Jul 2010 14:35:35 -0300 [thread overview]
Message-ID: <1278696935.10421.139.camel@localhost.localdomain> (raw)
In-Reply-To: <4C375658.10904@codeaurora.org>
Hi Ron,
> >> void register_public_browse_group(void)
> >> diff --git a/src/sdpd.h b/src/sdpd.h
> >> index e93b0b6..8fd8bbe 100644
> >> --- a/src/sdpd.h
> >> +++ b/src/sdpd.h
> >> @@ -6,6 +6,7 @@
> >> * Copyright (C) 2002-2003 Maxim Krasnyansky <maxk@qualcomm.com>
> >> * Copyright (C) 2002-2010 Marcel Holtmann <marcel@holtmann.org>
> >> * Copyright (C) 2002-2003 Stephen Crane <steve.crane@rococosoft.com>
> >> + * Copyright (C) 2010, Code Aurora Forum. All rights reserved.
> >
> > I prefer that we actually see major code contributions that justify a
> > copyright here before you start adding it. And so let the maintainers
> > worry about that later on. I don't wanna see just random copyright
> > additions for obvious fixes or changes that are most likely even derived
> > from existing code.
> >
>
> I'm unsure of the reasoning unless the idea is to add copyright markings
> to show attribution and level of contribution. In our case it's just a
> legal marking.
>
> If the reasoning for adding or not adding is the former, does this not
> rise to that level, and for my own education and future reference why not?
we normally automatically add the copyright for companies or individual
when they make large contributions. Not just small extensions or fixes
where it is questionable if they are copyrightable anyway.
For just tracking contributions, we have GIT :)
Regards
Marcel
next prev parent reply other threads:[~2010-07-09 17:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 22:08 [PATCH v2 0/3] Enhanced support for extended inquiry response Inga Stotland
2010-07-07 22:08 ` [PATCH 1/3] Support for adding UUID128 to " Inga Stotland
2010-07-08 17:17 ` Marcel Holtmann
2010-07-09 17:03 ` Ron Shaffer
2010-07-09 17:35 ` Marcel Holtmann [this message]
2010-07-30 19:13 ` Copyrights and Legal header ingas
2010-07-30 21:38 ` Marcel Holtmann
2010-07-07 22:08 ` [PATCH 2/3] Update EIR whenever record is added or removed Inga Stotland
2010-07-08 17:21 ` Marcel Holtmann
2010-07-07 22:08 ` [PATCH 3/3] Extended support for generating dictionary value of service UUIDs Inga Stotland
2010-07-08 11:36 ` Luiz Augusto von Dentz
2010-07-08 17:23 ` Marcel Holtmann
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=1278696935.10421.139.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=ingas@codeaurora.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=rshaffer@codeaurora.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