From dev-return-39522-archive-asf-public=cust-asf.ponee.io@subversion.apache.org Thu Oct 10 18:56:34 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 5CEB1180626 for ; Thu, 10 Oct 2019 20:56:34 +0200 (CEST) Received: (qmail 95483 invoked by uid 500); 10 Oct 2019 18:56:33 -0000 Mailing-List: contact dev-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@subversion.apache.org Received: (qmail 95460 invoked by uid 99); 10 Oct 2019 18:56:33 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Oct 2019 18:56:33 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id B8D85C2677 for ; Thu, 10 Oct 2019 18:56:32 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-ec2-va.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 8fxq1eEg13lb for ; Thu, 10 Oct 2019 18:56:30 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.167.172; helo=mail-oi1-f172.google.com; envelope-from=hartman.nathan@gmail.com; receiver= Received: from mail-oi1-f172.google.com (mail-oi1-f172.google.com [209.85.167.172]) by mx1-ec2-va.apache.org (ASF Mail Server at mx1-ec2-va.apache.org) with ESMTPS id 7A1FABC572 for ; Thu, 10 Oct 2019 18:46:44 +0000 (UTC) Received: by mail-oi1-f172.google.com with SMTP id k25so5800402oiw.13 for ; Thu, 10 Oct 2019 11:46:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=XIJoLJZ7+/8idUzCo5UlgvjmZYOyheQnPrWMTzNgIPM=; b=eZf4SjQs86kLmqe+CS23PqwHwqX7ZMbLixjaBKubB3nnNzOFQ5tTrYrWAzBFYy0U6e NQU6Y0kakMch3KxqJZDY57Ad7xoq/4rCkmcD1JVuiKhH6JKlor4SltKGEVdu4PcRTwwP b9fMFEX5NwER2T27DyKvR1oEvcunSEoeBYNEWj89n2vJ9yKIQSt71RkMPpnpU5CIORSR 7UL2Mb/brW8MmTk3or21Q6k4erWqmMZrTS2tMYuTRK8FB+YWmxZ+x1/Ic/7aMJUcjqfB PWYIEOxdSbbippOKkfqHVaYExhsT0LVXSW9CSkdKM7eBnnuXXaAaoj5exnISv+EBTdM9 AHGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=XIJoLJZ7+/8idUzCo5UlgvjmZYOyheQnPrWMTzNgIPM=; b=kTX4ifo6qlTVCsw8ZDh2OrTyUG9hBMBwcR0gvk52kigReNTpe9YP9SuN0C3tpsC1u5 9/X2x4S9M4D0N10Qg6d8bdWDNg0slGw2VinX7fyUdGfVsIHY+sGsC/OeNzwVWjavb8vu Uu7wgAfg7bTmt/XgqAaqaglgcY4wlr0+U/cLryOId6nHW3iAcj5GBm91K1gM25duLiJ5 wZfmu8/oquKg5Yh6k7CJfj7m+bF2v9zysjDu35YULW59k4yqadt7BKrd38qUekkpJ1iq kM601AMeE6bg3L4TJ9vyWr/tMN36/Y8MHi7yDsiqDNNS+vHfnvkK8/zmOccvY8Y2t4k1 DXZA== X-Gm-Message-State: APjAAAXC0YHvVqytiyZ/CHIQ6JpVRHBcKUf3THrHcwg48sdMdHORrD4n XeB+xzZ3DKEgZuSbShJk4tdiyJimbg2EjQyIiaQ= X-Google-Smtp-Source: APXvYqwg1bB+2CYpCU9hbo966n5abCGUpMkVIINLeIm9dIzPWq8C/XVjilMXYf3IcS3E0P/EDRtvorhCK9T69ODTW1U= X-Received: by 2002:aca:4584:: with SMTP id s126mr9057724oia.21.1570733203911; Thu, 10 Oct 2019 11:46:43 -0700 (PDT) MIME-Version: 1.0 References: <2f9bc052-7077-417c-8622-d3b33185873d@www.fastmail.com> <20191010171507.dvy3c5qk3pangrba@tarpaulin.shahaf.local2> In-Reply-To: From: Nathan Hartman Date: Thu, 10 Oct 2019 14:46:33 -0400 Message-ID: Subject: Re: PMCs: any Hackathon requests? (deadline 11 October) To: Daniel Shahaf Cc: Johan Corveleyn , Julian Foad , Subversion Developers Content-Type: multipart/alternative; boundary="000000000000a7f92a059492d28d" --000000000000a7f92a059492d28d Content-Type: text/plain; charset="UTF-8" On Thu, Oct 10, 2019 at 1:48 PM Daniel Shahaf wrote: > Nathan Hartman wrote on Thu, 10 Oct 2019 17:36 +00:00: > > On Thu, Oct 10, 2019 at 1:15 PM Daniel Shahaf > wrote: > > > > > > Nathan Hartman wrote on Thu, Oct 10, 2019 at 10:24:28 -0400: > > > > * Documentation: > > > > > > > > - SVN-3914 - INSTALL: document how to compile with libmagic on > > > > Windows. > > > > https://issues.apache.org/jira/browse/SVN-3914?issueNumber=3914 > > > > > > This is a subtask of the next one, isn't it? > > > > I separated them because one is documentation, the other is Python > > programming. I tried to keep things organized by skill set. Also SVN-3914 > > didn't actually include updating the scripts (unless I missed something). > > > > Should these be re-merged into one item, as you had it before? > > That depends. _Do_ the Windows build scripts support libmagic? > Good question. I've never built SVN on Windows, only Unix, so I don't actually know. I can look at the build scripts but if someone knows the answer to this please chime in!! More below > We can include the github link but there was a whole discussion here > > about how pull requests were sitting there untouched, and there was no > > clean way to accept them and have them marked as such. Has that been > > fixed? If not, I'd rather avoid the confusion that would cause. Let me > > know... > > Sure, there's no point in recommending a patch submission channel that's > not easy for us to work with. However, there's a third option: post the > github link but ask patches to be emailed. (We should probably just add > the link to HACKING, though, in that case; it's not specific to this > event.) We could do that and monitor github during the event in case some participants don't notice the request to mail patches. But we should eventually figure out a better solution for that submission channel. --000000000000a7f92a059492d28d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Oct 10, 2019 at 1:48 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
<= div class=3D"gmail_quote">
Nathan Hartman wro= te on Thu, 10 Oct 2019 17:36 +00:00:
> On Thu, Oct 10, 2019 at 1:15 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrot= e:
> >
> > Nathan Hartman wrote on Thu, Oct 10, 2019 at 10:24:28 -0400:
> > > * Documentation:
> > >
> > >=C2=A0 =C2=A0- SVN-3914 - INSTALL: document how to compile wi= th libmagic on
> > >=C2=A0 =C2=A0 =C2=A0Windows.
> > >=C2=A0 =C2=A0 =C2=A0h= ttps://issues.apache.org/jira/browse/SVN-3914?issueNumber=3D3914
> >
> > This is a subtask of the next one, isn't it?
>
> I separated them because one is documentation, the other is Python
> programming. I tried to keep things organized by skill set. Also SVN-3= 914
> didn't actually include updating the scripts (unless I missed some= thing).
>
> Should these be re-merged into one item, as you had it before?

That depends.=C2=A0 _Do_ the Windows build scripts support libmagic?

Good question. I= 've never built SVN on Windows, only Unix, so I don't actually know= . I can look at the build scripts but if someone knows the answer to this p= lease chime in!!

More be= low

> We can include the github link but there was a whole discussion here > about how pull requests were sitting there untouched, and there was no=
> clean way to accept them and have them marked as such. Has that been > fixed? If not, I'd rather avoid the confusion that would cause. Le= t me
> know...

Sure, there's no point in recommending a patch submission channel that&= #39;s
not easy for us to work with.=C2=A0 However, there's a third option: po= st the
github link but ask patches to be emailed.=C2=A0 (We should probably just a= dd
the link to HACKING, though, in that case; it's not specific to this ev= ent.)

We could do= that and monitor github during the event in case some participants don'= ;t notice the request to mail patches.

But we should eventually figure out a better solution for th= at submission channel.

<= br>


--000000000000a7f92a059492d28d--