Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] Pushing PJSIP fixes upstream
Date: Thu, 17 Mar 2016 23:17:34 +0100	[thread overview]
Message-ID: <56EB2CFE.4040002@lucaceresoli.net> (raw)

Dear Natanael Copa,

I am a contributor to the Buildroot embedded Linux build system [0].

Buildroot contains recipes to build packages and I recently added one
for PJSIP [1]. The initial recipe did not build with musl, so I took a
patch [2] that you added to Alpine Linux to fix the same problem.

The patch works as expected, thanks! Now it is in Buildroot, except I
split it in two and added some commentary, but I didn't change the code.

Now I would like these changes to be pushed to mainline PJSIP, so
everyone can benefit in the future and Alpine Linux, Buildroot and
probably other projects can drop a patch (BTW, upstreaming fixes is the
policy for Buildroot packages for these reasons).

I would have pushed the patches myself to the PJSIP developers, but the
Copyright Assignment they have does not allow me to do so because I am
not the original author [3].

For the above reasons, I'd like to ask you whether you are the original
author of the patch.

If you are, would you like to either push the patch upstream yourself or
to give me a written permission to do so under the Agreement?

If you aren't, can you point me to whoever you took the patch from, so I
can forward my request up to the original author?

Thanks in advance.

[0] https://buildroot.org/
[1] https://git.buildroot.net/buildroot/tree/package/libpjsip
[2]
http://git.alpinelinux.org/cgit/aports/commit/main/pjproject/musl-fixes.patch?id=f7dd9f9c08bd3bc49ef62ec7a394bd73e89766d2
[3]
http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/2016-March/019039.html

-- 
Luca

                 reply	other threads:[~2016-03-17 22:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=56EB2CFE.4040002@lucaceresoli.net \
    --to=luca@lucaceresoli.net \
    --cc=buildroot@busybox.net \
    /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