If you think they're ready to abandoned, you should be able to just abandon them.
Setting up auto-abandon requires a Gerrit restart. I haven't been able to prioritize one due to release/branching schedules. It's most likely to not happen until 3.12 is released. On Thu, Jul 27, 2017 at 10:06 AM, Raghavendra Gowdappa <rgowd...@redhat.com> wrote: > A Gentle reminder. > > @everyone, > > Do we've a process to be followed in this scenario? > > regards, > Raghavendra > > ----- Original Message ----- > > From: "Raghavendra Gowdappa" <rgowd...@redhat.com> > > To: "Nigel Babu" <nig...@redhat.com> > > Cc: "GlusterFS Maintainers" <maintain...@gluster.org>, "Gluster Devel" < > gluster-devel@gluster.org> > > Sent: Wednesday, July 19, 2017 10:33:39 AM > > Subject: List of patches that can be abandoned > > > > Hi all, > > > > In sync with our cleanup efforts, I think following patches can be > abandoned. > > If any of you've any concerns, please voice them out and we can discuss. > > > > https://review.gluster.org/11553 > > https://review.gluster.org/9623 > > https://review.gluster.org/5908 > > https://review.gluster.org/11734/ > > > > @Nigel, > > > > Since I don't have permissions to abandon these patches, can you do the > same? > > > > regards, > > Raghavendra > -- nigelb
_______________________________________________ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
