[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

How to manage PR's (was: [GitHub] subversion pull request #6: VC should be 14.1 and not 15.0)

From: Johan Corveleyn <jcorvel_at_gmail.com>
Date: Tue, 10 Oct 2017 22:02:03 +0200

On Tue, Oct 10, 2017 at 8:11 PM, asfgit <git_at_git.apache.org> wrote:
> Github user asfgit closed the pull request at:
>
> https://github.com/apache/subversion/pull/6
>
>
> ---

Anybody knows why asfgit closed the PR?

I've clicked on the above hyperlink, and saw some comments made by
Julian (11 hours ago) and by the submitter (8 hours ago), but these
comments are not visible on dev@. Shouldn't those be synced back here
somehow? Or how should we handle PR's, preferably with a process
that's still centered around the dev@ mailinglist?

If we can't really handle PR's well, maybe we shouldn't allow them
(i.e. indicate this on github somehow, that it's just a mirror and we
won't accept PR's, but expect patch submissions on dev@ instead)?

-- 
Johan
Received on 2017-10-10 22:02:29 CEST

This is an archived mail posted to the Subversion Dev mailing list.