[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200601.110044.945252928135960732.davem@davemloft.net>
Date: Mon, 01 Jun 2020 11:00:44 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: Jason@...c4.com
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH net-next 0/1] wireguard column reformatting for end of
cycle
From: "Jason A. Donenfeld" <Jason@...c4.com>
Date: Mon, 1 Jun 2020 00:29:45 -0600
> This is a series of 1, and the sole patch inside of it has justification
> regarding that patch itself. But I thought I'd mention in the cover
> letter that this is being sent right at the tail end of the net-next
> cycle, before you close it tomorrow afternoon, so that when net-next
> subsequently opens up, this patch has already made it to net, and we
> don't have any hassles with merges. I realize that in general this isn't
> the type of patch anyone really likes because of the merge hassle, but I
> think the timing is right for it, and WireGuard is still young enough
> that this should be still pretty easily possible.
This is going to make nearly every -stable backport not apply cleanly,
which is a severe burdon for everyone having to maintain stable trees.
I'm not applying this, sorry Jason.
Powered by blists - more mailing lists