Re: Way to unsubscribe from mailing lists

On 25/04/17 16:11, Michael Shuler wrote: > Many lists include a footer that have unsub info - does ezmlm support > footer append? I wouldn't mind it, if it helps users, and it seems > simpler than trying to filter random messages. Yes it does. And the default footer includes unsubscribe info.

Re: Review of Cassandra actions

On 07/11/2016 10:52, Benedict Elliott Smith wrote: > Hi Mark, > > Thanks, that was a calm and diplomatic email. > > recognise where they might need to apologise > > > I will start the ball rolling here, as I have not always been generous in > my interpretations of others' actions, and have

Re: Review of Cassandra actions

For the sake of clarity I am a member of the ASF board but I am not speaking on behalf of the board in this email. On 06/11/2016 01:25, Jeff Jirsa wrote: > I hope the other 7 members of the board take note of this response, > and other similar reactions on dev@ today. I can't speak for all seven

Re: Moderation

On 04/11/2016 15:47, Chris Mattmann wrote: > Hi Folks, > > Kelly Sommers sent a message to dev@cassandra and I'm trying to figure out if > it's in moderation. > > Can the moderators speak up? Using my infra karma, I checked the mail server. That message is waiting for moderator approval. It

Re: #cassandra-dev IRC logging

On 26/08/2016 19:17, Jason Brown wrote: > +1. How/where will this run? Is there any apache infra that we can make use > of? Don't know. Checking... Mark > > On Fri, Aug 26, 2016 at 10:48 AM, Jake Luciani wrote: > >> +1 so long as it filters out the join/leave stuff :) >>

Re: Github pull requests

C currently has the ability to directly close PRs on GitHub. This is one of the things on the infra TODO list that is being looked at. You can close them via a commit comment that the ASF GitHub tooling picks up. Mark > > -- > AY > > On 26 August 2016 at 17:07:29, Mark Thomas (ma..

Re: Github pull requests

On 26/08/2016 16:33, Jonathan Ellis wrote: > Hi all, > > Historically we've insisted that people go through the process of creating > a Jira issue and attaching a patch or linking a branch to demonstrate > intent-to-contribute and to make sure we have a unified record of changes > in Jira. > >

Re: 3.8/3.9 releases/branch freeze, current merge order

gt; > -- > AY > > On 24 August 2016 at 20:23:04, Mark Thomas (ma...@apache.org) wrote: > > On 24/08/2016 16:44, Aleksey Yeschenko wrote: > > > >> Also, cassandra-3.8 branch was removed from the repo, to further minimise >> confusion. > > That

Re: 3.8/3.9 releases/branch freeze, current merge order

On 24/08/2016 16:44, Aleksey Yeschenko wrote: > Also, cassandra-3.8 branch was removed from the repo, to further minimise > confusion. That is the sort of thing I'd expect to see discussed on the dev list first. Where is that discussion? Mark