From: Jason Dusek <jason.dusek@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH] Handle (a) changes in Screech and (b) borrow issue
Date: Fri, 17 Feb 2017 18:39:06 +0000 [thread overview]
Message-ID: <CAO3NbwMUYfaCbGuwHLET3Q8MzC2Xz7X6HMPyM6iT1rVO7VXzgA@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9pbvZoJ16PkDVQEMo7OGx16QFg1H4PxXkS4iSqheabDmg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
Hi Jason,
It was necessary to "vendor" Screech. A separate Git repo makes for a
cleaner patch than downloading and including all of Screech. The patch
makes some stuff public again that was once public and then went private:
https://github.com/solidsnack/screech/commit/6d91d075ad2f98f03c807a471953495c720a5696
I assume Trevor made them private for a reason; but also that the original
developer of the client used them for a reason. I would like to better
understand the application before making a suggestion as regards the
Screech API; but I would also really like the Rust client to build (as I
think we all would).
Kind Regards,
Jason
Jason A. Donenfeld <Jason@zx2c4.com> schrieb am Fr. 17. Feb. 2017 um 05:50:
> Hey,
>
> Thanks for the patch. This changes the screech repository to your own.
> Has Trevor agreed for you to officially take over that project? If so,
> please link me to the moderncrypto mailing list post about this. If
> not, why should things switch to yours rather than moving your patches
> upstream to Trevor?
>
> Regards,
> Jason
>
[-- Attachment #2: Type: text/html, Size: 1634 bytes --]
prev parent reply other threads:[~2017-02-17 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 5:09 Jason Dusek
2017-02-17 13:50 ` Jason A. Donenfeld
2017-02-17 18:39 ` Jason Dusek [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=CAO3NbwMUYfaCbGuwHLET3Q8MzC2Xz7X6HMPyM6iT1rVO7VXzgA@mail.gmail.com \
--to=jason.dusek@gmail.com \
--cc=Jason@zx2c4.com \
--cc=wireguard@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).