Open Stack

On Fri, Jul 25, 2014 at 06:38:29AM -0400, Sean Dague wrote:
> On 07/25/2014 01:18 AM, Ian Wienand wrote:
> > On 07/16/2014 11:15 PM, Alexis Lee wrote:
> >> What do you think about allowing some text after the words "recheck no
> >> bug"?
> > 
> > I think this is a good idea; I am often away from a change for a bit,
> > something happens in-between and Jenkins fails it, but chasing it down
> > days later is fairly pointless given how fast things move.
> > 
> > It would be nice if I could indicate "I thought about this".  In fact,
> > there might be an argument for *requiring* a reason
> > 
> > I proposed [1] to allow this
> > 
> > -i
> > 
> > [1] https://review.openstack.org/#/c/109492/
> 
> At the QA / Infra meetup we actually talked about the recheck syntax,
> and to change the way elastic recheck is interacting with the user.
> 
> https://review.openstack.org/#/q/status:open+project:openstack-infra/elastic-recheck+branch:master+topic:erchanges,n,z
> 
> and
> 
> https://review.openstack.org/#/q/status:open+project:openstack-infra/config+branch:master+topic:er,n,z
> 
> Are the result of that. Basically going forward we'll just support
> 
> 'recheck.*'

I'm not sure I understand what you mean by that ? Are we going to
use the literal string 'recheck.*' or do you mean we'll use 'recheck'
and the user can put arbitrary text after it ?

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|