From: Chris Talbot <chris@talbothome.com>
To: ofono@ofono.org, netdev@vger.kernel.org,
debian-on-mobile-maintainers@alioth-lists.debian.net,
librem-5-dev@lists.community.puri.sm, 982250@bugs.debian.org,
985893@bugs.debian.org
Subject: Forking on MMSD
Date: Wed, 14 Apr 2021 14:21:04 -0400 [thread overview]
Message-ID: <634e0debea558b90af2cebfc99518071f1d630e9.camel@talbothome.com> (raw)
In-Reply-To: <051ae8ae27f5288d64ec6ef2bd9f77c06b829b52.camel@talbothome.com>
Hello All,
In talking to the Debian Developer Mr. Federico Ceratto, since I have
been unable to get a hold of the Ofono Maintainers, the best course of
action for packaging mmsd into Debian is to simply fork the project and
submit my version upstream for packaging in Debian. My repository is
here: https://source.puri.sm/kop316/mmsd/
I am sending this so the relavent parties are aware of this, and to
indicate that I no longer intend on trying to get a hold of upstream
mmsd to try and submit patches.
For the Purism Employees, I am additionally asking for permission to
keep hosting mmsd on https://source.puri.sm/ . I have been extremely
appreciative in using it and I am happy to keep it there, but I want to
be neighboorly and ask if it is okay for me to keep it there. If it is
not, I completely understand and I am fine with moving it to a new
host.
If you have any questions, comments, or concern, please reach out to
me.
--
Respectfully,
Chris Talbot
next prev parent reply other threads:[~2021-04-14 18:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 14:13 [PATCH 0/9] Updates for mmsd Chris Talbot
2021-04-10 14:17 ` [PATCH 1/9] Fix mmsd to work with T-mobile Chris Talbot
2021-04-10 14:20 ` [PATCH 2/9] Ensure Compatibility with Telus Canada Chris Talbot
2021-04-10 14:20 ` [PATCH 3/9] Ensure Compatibility with AT&T Chris Talbot
2021-04-10 14:21 ` [PATCH 4/9] Fix issue if there is an empty string in encoded text Chris Talbot
2021-04-10 14:22 ` [PATCH 5/9] Allow for a user configurable maximum attachment size Chris Talbot
2021-04-10 14:22 ` [PATCH 6/9] Update README Chris Talbot
2021-04-10 14:23 ` [PATCH 7/9] Fix Draft and Sent Bugs Chris Talbot
2021-04-10 14:23 ` [PATCH 8/9] Allow Maintainer mode to compile without -WError Chris Talbot
2021-04-10 14:24 ` [PATCH 9/9] Enable support for Modem Manager Chris Talbot
2021-04-14 18:21 ` Chris Talbot [this message]
2021-04-14 18:30 ` [Debian-on-mobile-maintainers] Forking on MMSD Guido Günther
2021-04-14 18:46 ` Chris Talbot
2021-04-15 9:10 ` Guido Günther
2021-04-14 18:39 ` Marius Gripsgard
2021-04-14 22:09 ` Bug#985893: " Wookey
2021-04-15 0:12 ` Chris Talbot
2021-04-14 19:29 ` Pavel Machek
2021-04-14 21:11 ` Bug#985893: " Paul Wise
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=634e0debea558b90af2cebfc99518071f1d630e9.camel@talbothome.com \
--to=chris@talbothome.com \
--cc=982250@bugs.debian.org \
--cc=985893@bugs.debian.org \
--cc=debian-on-mobile-maintainers@alioth-lists.debian.net \
--cc=librem-5-dev@lists.community.puri.sm \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).