As nobody seems to object, you can now find a patch for the proposed
document in the corresponding Jira ticket:
https://issues.apache.org/jira/browse/CASSANDRA-13256
On 03/17/2017 08:33 PM, Stefan Podkowinski wrote:
> There's recently been a discussion about the wiki and how we should
> continue
> > On 2017-03-17 12:33 (-0700), Stefan Podkowinski wrote:
> >
> >> As you can see there's a large part about using GitHub for editing on
> >> the page. I'd like to know what you think about that and if you'd agree
> >> to accept PRs for such purposes.
I don't want to bury the important point i
On 2017-03-17 13:06 (-0700), benjamin roth wrote:
> Isn't there a way to script that with just a few lines of python or
> whatever?
For docs, probably. Real patches are harder.
There's a minor problem that they're a bit spammy (all PRs create dev@ emails),
but I'd rather tolerate that nois
I don't see how that would be harder compared to merging a patch
attached to a jira ticket. If you'd want to merge my PR you'd just have
to do something like that:
curl -o docs.patch
https://github.com/apache/cassandra/compare/trunk...spodkowinski:docs_gettingstarted.patch
git am docs.patch
git re
Isn't there a way to script that with just a few lines of python or
whatever?
2017-03-17 21:03 GMT+01:00 Jeff Jirsa :
>
>
> On 2017-03-17 12:33 (-0700), Stefan Podkowinski wrote:
>
> > As you can see there's a large part about using GitHub for editing on
> > the page. I'd like to know what you t
On 2017-03-17 12:33 (-0700), Stefan Podkowinski wrote:
> As you can see there's a large part about using GitHub for editing on
> the page. I'd like to know what you think about that and if you'd agree
> to accept PRs for such purposes.
>
The challenge of github PRs isn't that we don't want t
