Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Egbert Verhage <egbert@eggiecode.org>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] Seeking Ubuntu PPA Maintainer
Date: Wed, 16 Nov 2016 15:09:20 +0100	[thread overview]
Message-ID: <CAHmME9rPPxnKWDXYv7r=GjrAoSaMqPRhdALmGxHbRV9v5uC48A@mail.gmail.com> (raw)
In-Reply-To: <67b97701-8286-039e-31bb-b7275ab338e8@eggiecode.org>

Hi Egbert,

On Wed, Nov 16, 2016 at 11:03 AM, Egbert Verhage <egbert@eggiecode.org> wrote:
> Going to update the PPA to remove my disable of AVX2.

Good. Can you remove this garbage immediately:
https://git.launchpad.net/wireguard/tree/debian/patches/update-hard-disable-patch-to-upstream
https://git.launchpad.net/wireguard/tree/debian/patches/0001-disable-hard-avx2

There are two principles I would like to see adamantly applied before
I'll endorse this PPA:

1. Stay as close to vanilla upstream snapshots as possible. Do not
have patches that differ from Debian's too much. If you need changes,
consult the very active and very willing upstream instead.
2. Only package snapshots. Do not choose your own git commits.

Are these two things you're willing to do?

Thanks,
Jason

  reply	other threads:[~2016-11-16 14:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15 20:44 Jason A. Donenfeld
2016-11-15 23:41 ` Egbert Verhage
     [not found] ` <454ad249-3313-9423-c2d4-7602d56849fc@eggiecode.org>
2016-11-16  0:12   ` Jason A. Donenfeld
2016-11-16  0:34     ` Egbert Verhage
2016-11-16  1:31       ` Jason A. Donenfeld
2016-11-16  6:20         ` Dan Luedtke
2016-11-16 11:18           ` Egbert Verhage
2016-11-16 11:34             ` Dan Lüdtke
2016-11-16 14:04               ` Jason A. Donenfeld
2016-11-16 10:03         ` Egbert Verhage
2016-11-16 14:09           ` Jason A. Donenfeld [this message]
2016-11-16 14:22             ` Egbert Verhage
2016-11-16 14:25               ` Jason A. Donenfeld
2016-11-16  6:45       ` Daniel Kahn Gillmor
2016-11-16 11:10         ` Egbert Verhage
2016-11-16 14:24           ` Jason A. Donenfeld
2016-11-16 22:17             ` Daniel Kahn Gillmor
2016-11-16 22:52               ` Jason A. Donenfeld
2016-11-16 14:11 ` Jason A. Donenfeld
2016-11-16 14:37 Anonymous Anonymous
2016-11-16 15:00 ` Jason A. Donenfeld
2016-11-16 15:08   ` Egbert Verhage
2016-11-16 14:47 Anonymous Anonymous

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='CAHmME9rPPxnKWDXYv7r=GjrAoSaMqPRhdALmGxHbRV9v5uC48A@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=egbert@eggiecode.org \
    --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).