From: Thierry Merle <thierry.merle@free.fr>
To: Hans de Goede <j.w.r.degoede@hhs.nl>
Cc: video4linux-list@redhat.com, v4l2 library <v4l2-library@linuxtv.org>
Subject: Re: PATCH: libv
Date: Thu, 03 Jul 2008 22:15:54 +0200 [thread overview]
Message-ID: <486D337A.4060206@free.fr> (raw)
In-Reply-To: <486D3306.7080009@hhs.nl>
Hans de Goede a écrit :
> Thierry Merle wrote:
>> Hans de Goede a écrit :
>>> Hi All,
>>>
>>> This patch adds support to libv4l for the compressed bayer format
>>> emitted by
>>> pac207 based cams.
>>>
>>> Signed-off-by: Hans de Goede <j.w.r.degoede@hhs.nl>
>>>
>>> Regards,
>>>
>>> Hans
>> Applied on http://www.linuxtv.org/hg/~tmerle/v4l2-library
>> Is it necessary to add the emails about license authorizations in the
>> sources?
>
> I dunno IANAL, but within Fedora (where I'm a packager) the guy
> responsible for the legal stuff, in case of license changes always
> wants a "written" (email is ok) permission notice bundled with the
> sources, so I followed this example, we could put the permission
> notices in some other file, but I think its good practice to keep them
> around bundled with the sources. I deliberately put them at the end so
> that with normal editing they don't get in the way.
>
OK if it is mandatory, continue to put it at the closest place from the
concerned source code.
> Actually I'm about to submit a patch to add a permission notice for
> the sn9c10x decompression algorithm as I didn't write that myself.
>
OK
> Regards,
>
> Hans
>
> p.s.
>
> Sorry about the semi missing subject last mail.
>
I corrected it by myself :)
Thierry
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
prev parent reply other threads:[~2008-07-03 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 19:49 PATCH: libv Hans de Goede
2008-07-03 20:04 ` Thierry Merle
2008-07-03 20:13 ` Hans de Goede
2008-07-03 20:15 ` Thierry Merle [this message]
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=486D337A.4060206@free.fr \
--to=thierry.merle@free.fr \
--cc=j.w.r.degoede@hhs.nl \
--cc=v4l2-library@linuxtv.org \
--cc=video4linux-list@redhat.com \
/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