| 1 |
El sáb, 01-11-2014 a las 10:47 +0000, Diego Elio Pettenò escribió: |
| 2 |
> On 1 November 2014 00:18, Rich Freeman <rich0@g.o> wrote: |
| 3 |
> > So, if there is a better way, I'm all ears for constructive |
| 4 |
> > suggestions. By constructive I mean that somebody who comes up with a |
| 5 |
> > script that automatically retrieves build logs and attaches them to |
| 6 |
> > bugs is being more helpful than somebody who says that somebody else |
| 7 |
> > should come up with such a script, and so on. That doesn't mean that |
| 8 |
> > we can't talk about solutions before we build them - only that it |
| 9 |
> > isn't helpful when we basically demand that others build them for us. |
| 10 |
> |
| 11 |
> Let me try to be clear (once again) of what the problem is. Even just |
| 12 |
> spending time rewriting this irks me because I have written, repeated, |
| 13 |
> re-explained, described the problem a number of times, between bugs, |
| 14 |
> this ML and my blog ( https://blog.flameeyes.eu/tag/tinderbox ). |
| 15 |
[...] |
| 16 |
|
| 17 |
Would be possible to change the script opening the bug reports to CC |
| 18 |
somebody to the bugs assigned to vapier? For example, when metadata.xml |
| 19 |
causes the bug assigned to him, the script could additionally CC other |
| 20 |
people (like me) that could handle the build.log stuff |
Archives