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

2017-10-10 Thread James McCoy
On Wed, Oct 11, 2017 at 12:51:34AM +, Daniel Shahaf wrote: > Stefan Sperling wrote on Tue, 10 Oct 2017 23:44 +0200: > > Couldn't some automated process mail PRs from github as (--git) diffs to > > dev@? > > Moreover, if the submitter's commits have a valid email address on them > (and the dom

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

2017-10-10 Thread Daniel Shahaf
Paul Hammant wrote on Tue, 10 Oct 2017 17:32 -0400: > If you ask people comfortable with donating code via PR to email patches > (or similar) to dev@ instead, you'll get a 1/100th contribution rate. Or > worse. FWIW my experience is the opposite. On $otherproject we also receive patches via email

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

2017-10-10 Thread Daniel Shahaf
Stefan Sperling wrote on Tue, 10 Oct 2017 23:44 +0200: > Couldn't some automated process mail PRs from github as (--git) diffs to dev@? Moreover, if the submitter's commits have a valid email address on them (and the domain doesn't use strict SPF records), that automated process can even set the "

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

2017-10-10 Thread Daniel Shahaf
Jacek Materna wrote on Tue, 10 Oct 2017 16:47 -0500: > There's webhooks in place yes- we could setup a middleman like zapier to > send "records" via an exchange for archive purposes. More than happy to > setup or help setup. Typical use case Johan, for those wanting a "log" of > github activity. >

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

2017-10-10 Thread Jacek Materna
There's webhooks in place yes- we could setup a middleman like zapier to send "records" via an exchange for archive purposes. More than happy to setup or help setup. Typical use case Johan, for those wanting a "log" of github activity. Thoughts? -jacek On Tue, Oct 10, 2017 at 4:44 PM, Stefan Spe

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

2017-10-10 Thread Stefan Sperling
On Tue, Oct 10, 2017 at 05:32:21PM -0400, Paul Hammant wrote: > > > > > > 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@.

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

2017-10-10 Thread Paul Hammant
> > > 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,

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

2017-10-10 Thread Johan Corveleyn
On Tue, Oct 10, 2017 at 8:11 PM, asfgit 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 th

[GitHub] subversion pull request #6: VC should be 14.1 and not 15.0

2017-10-10 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/subversion/pull/6 ---

[GitHub] subversion pull request #6: VC should be 14.1 and not 15.0

2017-10-07 Thread atkawa7
GitHub user atkawa7 opened a pull request: https://github.com/apache/subversion/pull/6 VC should be 14.1 and not 15.0 You can merge this pull request into a Git repository by running: $ git pull https://github.com/atkawa7/subversion patch-1 Alternatively you can review and ap