On 2019/10/20 13:46, Nathan Hartman wrote:
From the "Closing Old Issues" department:
SVN-1804: "mailer.py doesn't catch SMTPRecipientsRefused in finish()"
* Created and last updated in 2004.
* No comments in more than 15 years.
From my reading of this issue, the impact is that any mail delive
>From the "Closing Old Issues" department:
SVN-1804: "mailer.py doesn't catch SMTPRecipientsRefused in finish()"
* Created and last updated in 2004.
* No comments in more than 15 years.
>From my reading of this issue, the impact is that any mail delivery
hiccup may cause this hook script to exit
On Fri, Oct 18, 2019 at 5:00 PM Branko Čibej wrote:
> On 18.10.2019 21:39, Nathan Hartman wrote:
>> On Fri, Oct 18, 2019 at 2:40 PM Robert Dailey
wrote:
>>> CMake is really versatile and great for cross compiling.
>>>
>> I'm copying Brane because I recall some mention about CMake. Is it
>> alread
On 2019/10/20 8:37, Branko Čibej wrote:
On 20.10.2019 01:10, Yasuhito FUTATSUKI wrote:
On 2019/10/20 6:59, Branko Čibej wrote:
On 19.10.2019 23:06, Branko Čibej wrote:
On 19.10.2019 19:55, Branko Čibej wrote:
On 19.10.2019 11:45, Yasuhito FUTATSUKI wrote:
On 2019/10/18 8:39, Branko Čibej wro
Nathan Hartman wrote on Sun, 20 Oct 2019 01:49 +00:00:
> I support this idea even if the soak must restart or be extended.
Brainstorming: How about letting the soak continue but documenting in
the release notes, release announcements, etc., that we'll be adding swig-
py3 support in a patch release
On Sat, Oct 19, 2019 at 2:11 PM Branko Čibej wrote:
> By the principle of least surprise, I think it
> would be better to merge to trunk, create a
> new 1.13.0 release candidate
+1
> and (maybe?) restart the soak.
I support this idea even if the soak must restart or be extended.
Rationale:
*
On 20.10.2019 01:10, Yasuhito FUTATSUKI wrote:
> On 2019/10/20 6:59, Branko Čibej wrote:
>> On 19.10.2019 23:06, Branko Čibej wrote:
>>> On 19.10.2019 19:55, Branko Čibej wrote:
On 19.10.2019 11:45, Yasuhito FUTATSUKI wrote:
> On 2019/10/18 8:39, Branko Čibej wrote:
>> On 17.10.2019 23
On 2019/10/20 6:59, Branko Čibej wrote:
On 19.10.2019 23:06, Branko Čibej wrote:
On 19.10.2019 19:55, Branko Čibej wrote:
On 19.10.2019 11:45, Yasuhito FUTATSUKI wrote:
On 2019/10/18 8:39, Branko Čibej wrote:
On 17.10.2019 23:46, Branko Čibej wrote:
On 17.10.2019 23:01, Daniel Shahaf wrote:
On 19.10.2019 23:06, Branko Čibej wrote:
> On 19.10.2019 19:55, Branko Čibej wrote:
>> On 19.10.2019 11:45, Yasuhito FUTATSUKI wrote:
>>> On 2019/10/18 8:39, Branko Čibej wrote:
On 17.10.2019 23:46, Branko Čibej wrote:
> On 17.10.2019 23:01, Daniel Shahaf wrote:
>> Branko Čibej wrote o
On 19.10.2019 19:55, Branko Čibej wrote:
> On 19.10.2019 11:45, Yasuhito FUTATSUKI wrote:
>> On 2019/10/18 8:39, Branko Čibej wrote:
>>> On 17.10.2019 23:46, Branko Čibej wrote:
On 17.10.2019 23:01, Daniel Shahaf wrote:
> Branko Čibej wrote on Thu, Oct 17, 2019 at 22:56:29 +0200:
>> On
On 19.10.2019 12:06, Johan Corveleyn wrote:
> On Sat, Oct 19, 2019 at 1:23 AM Daniel Shahaf wrote:
>> Yasuhito FUTATSUKI wrote on Fri, Oct 18, 2019 at 23:09:19 +0900:
>>> On 2019/10/16 21:12, Johan Corveleyn wrote:
This makes me wonder: should that be fixed specifically on trunk, and
nom
On 19.10.2019 11:45, Yasuhito FUTATSUKI wrote:
> On 2019/10/18 8:39, Branko Čibej wrote:
>> On 17.10.2019 23:46, Branko Čibej wrote:
>>> On 17.10.2019 23:01, Daniel Shahaf wrote:
Branko Čibej wrote on Thu, Oct 17, 2019 at 22:56:29 +0200:
> On 17.10.2019 22:37, Daniel Shahaf wrote:
>> B
On Sat, Oct 19, 2019 at 1:23 AM Daniel Shahaf wrote:
>
> Yasuhito FUTATSUKI wrote on Fri, Oct 18, 2019 at 23:09:19 +0900:
> > On 2019/10/16 21:12, Johan Corveleyn wrote:
> > > This makes me wonder: should that be fixed specifically on trunk, and
> > > nominated for backport to 1.13, so we can poss
On 2019/10/18 8:39, Branko Čibej wrote:
On 17.10.2019 23:46, Branko Čibej wrote:
On 17.10.2019 23:01, Daniel Shahaf wrote:
Branko Čibej wrote on Thu, Oct 17, 2019 at 22:56:29 +0200:
On 17.10.2019 22:37, Daniel Shahaf wrote:
Branko Čibej wrote on Thu, 17 Oct 2019 06:49 +00:00:
On 16.10.2019 1
14 matches
Mail list logo
