[Gluster-devel] List of patches that can be abandoned

Nigel Babu nigelb at redhat.com
Thu Jul 27 06:09:59 UTC 2017


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 <rgowdapp at 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" <rgowdapp at redhat.com>
> > To: "Nigel Babu" <nigelb at redhat.com>
> > Cc: "GlusterFS Maintainers" <maintainers at gluster.org>, "Gluster Devel" <
> gluster-devel at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20170727/0f115621/attachment.html>


More information about the Gluster-devel mailing list