Excerpts from Brendan Jones's message of Fri Dec 16 00:32:24 +0100 2011:
On 12/15/2011 09:57 PM, Brendan Jones wrote:
On 11/21/2011 02:14 PM, Stanislav Ochotnicky wrote:
Hello fellow devs,
I am sure quite a few of you have done some reviews and thought Hey,
a,b,c and d could be
On 2011-12-19 10:32, Stanislav Ochotnicky wrote:
I can tell you right now that cornercases will never be caught with
tools like this. Licensecheck only looks at headers/comments, whereas
licensing depends on many things and can be quite confusing. I am sure
that rpmdevtools maintainers would
On 16.12.2011 00:32, Brendan Jones wrote:
Not sure if this is something which should be part of this package or
another entirely?
Sure, we will reinvent the wheel yet again (see
http://www.fossology.org/ ... yes it would probably require some
fedora-wide server, or maybe not, I don't know
On 11/21/2011 02:14 PM, Stanislav Ochotnicky wrote:
Hello fellow devs,
I am sure quite a few of you have done some reviews and thought Hey,
a,b,c and d could be automated. For E I could use some more
information that can be automatically gathered. Some of you even
wrote your own tools to do
On 12/15/2011 09:57 PM, Brendan Jones wrote:
On 11/21/2011 02:14 PM, Stanislav Ochotnicky wrote:
Hello fellow devs,
I am sure quite a few of you have done some reviews and thought Hey,
a,b,c and d could be automated. For E I could use some more
information that can be automatically gathered.
On 11/21/2011 02:14 PM, Stanislav Ochotnicky wrote:
- Any ideas, bugreports etc will be much appreciated
I would be very interested in feature, which instead of mock, will run
Koji scratch build and then will download resulting packages from Koji.
--
Miroslav Suchy
Red Hat Satellite
On Mon, 2011-12-05 at 17:06 +0100, Miroslav Suchý wrote:
On 11/21/2011 02:14 PM, Stanislav Ochotnicky wrote:
- Any ideas, bugreports etc will be much appreciated
I would be very interested in feature, which instead of mock, will run
Koji scratch build and then will download resulting
Hello fellow devs,
I am sure quite a few of you have done some reviews and thought Hey,
a,b,c and d could be automated. For E I could use some more
information that can be automatically gathered. Some of you even
wrote your own tools to do some of these things.
Yet there is no unified tool, nor
On 11/21/2011 01:14 PM, Stanislav Ochotnicky wrote:
Hello fellow devs,
I am sure quite a few of you have done some reviews and thought Hey,
a,b,c and d could be automated. For E I could use some more
information that can be automatically gathered. Some of you even
wrote your own tools to do
On Mon, 2011-11-21 at 13:25 +, Jóhann B. Guðmundsson wrote:
On 11/21/2011 01:14 PM, Stanislav Ochotnicky wrote:
Hello fellow devs,
I am sure quite a few of you have done some reviews and thought Hey,
a,b,c and d could be automated. For E I could use some more
information that can be
Excerpts from Jóhann B. Guðmundsson's message of Mon Nov 21 14:25:22 +0100
2011:
[1] https://fedorahosted.org/FedoraReview
[2] https://fedorahosted.org/FedoraReview/browser/api/README
Is this not something that releng/autoqa could use as well as in run
against all already existing specs
Well there may be a chance this tool may eventually become officially
adopted by QA after it gets tested and used long enough to consider it
safe/stable.
On Mon, Nov 21, 2011 at 7:48 AM, Stanislav Ochotnicky
sochotni...@redhat.com wrote:
Excerpts from Jóhann B. Guðmundsson's message of Mon Nov
12 matches
Mail list logo
