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
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
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 "
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.
>
I am wondering if there has been any progress on this. I just ran into the
same problem.
--
Sent from: http://subversion.1072662.n5.nabble.com/Subversion-Dev-f4725.html
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
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@.
>
>
> 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,
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 user asfgit closed the pull request at:
https://github.com/apache/subversion/pull/6
---
Well pipelining into Svn's HTTP 1.1 interface does work as you suggested.
There is a library in Python called 'hyper' that does it -
http://hyper.readthedocs.io/en/latest/quickstart.html#streams though the
example get_response signature is not current (I raised a bug). Also, if I
change HTTPConne
Yikes! I'll have to run through the build setup for Subversion - 52 pages
of requirements *before* launching ./config, right? - including
wind-of-newt, left handed screwdriver, *two* four-leaf clovers ;) :-P
Seriously: sounds good - and I appreciate it :)
On 10.10.2017 16:02, Paul Hammant wrote:
> As my forthcoming multi-user app that uses Subversion as a backing
> store is going to kill Svn it with Depth-∞ PROPFINDs from root, I
> really want to see this implemented.
>
> Because I can't wait
... I will implement a patch that exposes directory ch
As my forthcoming multi-user app that uses Subversion as a backing store is
going to kill Svn it with Depth-∞ PROPFINDs from root, I really want to see
this implemented.
Because I can't wait I will implement something that calculates SHA1s for
the directory in question, and drops it into a '.sha1'
14 matches
Mail list logo
