+1
2017-03-20 21:28 GMT-07:00 Amitkumar Ghatwal :
> +1
>
> [image: Inactive hide details for Michael Shuler ---03/21/2017 08:59:43
> AM---+1 On 03/20/2017 05:32 PM, Jeff Jirsa wrote:]Michael Shuler
> ---03/21/2017 08:59:43 AM---+1 On 03/20/2017 05:32 PM, Jeff Jirsa wrote:
>
> From: Michael Shuler
+1
From: Michael Shuler
To: dev@cassandra.apache.org
Date: 03/21/2017 08:59 AM
Subject:Re: [VOTE] Ask Infra to move github notification emails to pr@
Sent by:Michael Shuler
+1
On 03/20/2017 05:32 PM, Jeff Jirsa wrote:
> There's no reason for the dev list to get spa
+1
On 03/20/2017 05:32 PM, Jeff Jirsa wrote:
> There's no reason for the dev list to get spammed everytime there's a
> github PR. We know most of the time we prefer JIRAs for real code PRs, but
> with docs being in tree and low barrier to entry, we may want to accept
> docs through PRs ( see https
+1
On Mon, Mar 20, 2017 at 8:26 PM, jason zhao yang <
zhaoyangsingap...@gmail.com> wrote:
> +1
> On Tue, 21 Mar 2017 at 9:36 AM, Jonathan Haddad wrote:
>
> > +1
> > On Mon, Mar 20, 2017 at 6:33 PM Jason Brown
> wrote:
> >
> > > +1
> > > On Mon, Mar 20, 2017 at 18:21 Anthony Grasso >
> > > wrot
+1
On Tue, 21 Mar 2017 at 9:36 AM, Jonathan Haddad wrote:
> +1
> On Mon, Mar 20, 2017 at 6:33 PM Jason Brown wrote:
>
> > +1
> > On Mon, Mar 20, 2017 at 18:21 Anthony Grasso
> > wrote:
> >
> > > +1
> > >
> > > On 21 March 2017 at 09:32, Jeff Jirsa wrote:
> > >
> > > > There's no reason for the
+1
On Mon, Mar 20, 2017 at 6:33 PM Jason Brown wrote:
> +1
> On Mon, Mar 20, 2017 at 18:21 Anthony Grasso
> wrote:
>
> > +1
> >
> > On 21 March 2017 at 09:32, Jeff Jirsa wrote:
> >
> > > There's no reason for the dev list to get spammed everytime there's a
> > > github PR. We know most of the t
+1
On Mon, Mar 20, 2017 at 18:21 Anthony Grasso
wrote:
> +1
>
> On 21 March 2017 at 09:32, Jeff Jirsa wrote:
>
> > There's no reason for the dev list to get spammed everytime there's a
> > github PR. We know most of the time we prefer JIRAs for real code PRs,
> but
> > with docs being in tree an
+1
On 21 March 2017 at 09:32, Jeff Jirsa wrote:
> There's no reason for the dev list to get spammed everytime there's a
> github PR. We know most of the time we prefer JIRAs for real code PRs, but
> with docs being in tree and low barrier to entry, we may want to accept
> docs through PRs ( see
+1
Agreed. Changing vote to -1. Will re-open with Blake's idea.
On Mon, Mar 20, 2017 at 3:23 PM, Brandon Williams wrote:
> I retract my +1 and think instead we should open a vote on Blake's idea.
>
> On Mon, Mar 20, 2017 at 5:20 PM, Brandon Williams
> wrote:
>
> > I think this is a better solution
+1
On Mon, Mar 20, 2017 at 5:32 PM, Jeff Jirsa wrote:
> There's no reason for the dev list to get spammed everytime there's a
> github PR. We know most of the time we prefer JIRAs for real code PRs, but
> with docs being in tree and low barrier to entry, we may want to accept
> docs through PRs
+1
On March 20, 2017 at 3:33:16 PM, Jeff Jirsa (jji...@gmail.com) wrote:
There's no reason for the dev list to get spammed everytime there's a
github PR. We know most of the time we prefer JIRAs for real code PRs, but
with docs being in tree and low barrier to entry, we may want to accept
doc
There's no reason for the dev list to get spammed everytime there's a
github PR. We know most of the time we prefer JIRAs for real code PRs, but
with docs being in tree and low barrier to entry, we may want to accept
docs through PRs ( see https://issues.apache.org/jira/browse/CASSANDRA-13256
, and
I retract my +1 and think instead we should open a vote on Blake's idea.
On Mon, Mar 20, 2017 at 5:20 PM, Brandon Williams wrote:
> I think this is a better solution.
>
> On Mon, Mar 20, 2017 at 5:03 PM, Blake Eggleston
> wrote:
>
>> Maybe we should add p...@cassandra.apache.org or something an
I think this is a better solution.
On Mon, Mar 20, 2017 at 5:03 PM, Blake Eggleston
wrote:
> Maybe we should add p...@cassandra.apache.org or something and send them
> there? I don't subscribe to commits@ because it's too much email, I would
> be interested in being notified when a PR is opened
+1
On Mon, Mar 20, 2017 at 3:02 PM Brandon Williams wrote:
> +1, we've had to explain this a thousand times here.
>
> On Mon, Mar 20, 2017 at 5:00 PM, Jeff Jirsa wrote:
>
> > There's no reason for the dev list to get spammed everytime there's a
> > github PR. We know most of the time we prefer
Maybe we should add p...@cassandra.apache.org or something and send them there?
I don't subscribe to commits@ because it's too much email, I would be
interested in being notified when a PR is opened though.
On March 20, 2017 at 3:00:47 PM, Jeff Jirsa (jji...@gmail.com) wrote:
There's no reason
+1
On Mon, Mar 20, 2017 at 3:02 PM, Brandon Williams wrote:
> +1, we've had to explain this a thousand times here.
>
> On Mon, Mar 20, 2017 at 5:00 PM, Jeff Jirsa wrote:
>
> > There's no reason for the dev list to get spammed everytime there's a
> > github PR. We know most of the time we prefer
+1, we've had to explain this a thousand times here.
On Mon, Mar 20, 2017 at 5:00 PM, Jeff Jirsa wrote:
> There's no reason for the dev list to get spammed everytime there's a
> github PR. We know most of the time we prefer JIRAs for real code PRs, but
> with docs being in tree and low barrier t
There's no reason for the dev list to get spammed everytime there's a
github PR. We know most of the time we prefer JIRAs for real code PRs, but
with docs being in tree and low barrier to entry, we may want to accept
docs through PRs ( see https://issues.apache.org/jira/browse/CASSANDRA-13256
, and
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
Github user asfgit closed the pull request at:
https://github.com/apache/cassandra/pull/97
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is en
Github user MikkelTAndersen closed the pull request at:
https://github.com/apache/cassandra/pull/98
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feat
Github user jeffjirsa commented on the issue:
https://github.com/apache/cassandra/pull/98
Looks like this was committed as 0eebc6e6b7cd7fc801579e57701608e7bf155ee0 -
please do close the PR when you can (the project is unable to close it for you,
which is one of the reasons we tend not
GitHub user aertoria opened a pull request:
https://github.com/apache/cassandra/pull/100
clean up
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aertoria/cassandra trunk
Alternatively you can review and apply these changes as t
25 matches
Mail list logo
