On 08/01/2012 09:06 PM, Tang Chen wrote:
Hi Chris:
Thanks. :)
When you open up the tracking issue, please let me know. :)
On 08/02/2012 12:37 AM, Chris Evich wrote:
On 08/01/2012 04:05 AM, Tang Chen wrote:
Hi Chris~
Thanks for all the help.
I have opened up a tree on github:
https://github.com/imtangchen/autotest.git
I think our work in the future work can be sent to you as a pull request.
And also, I tried to use "issue" on github. But I'm not quit familiar with this
function now.
I and Yu Mingfei will start to use it in the near future.
I think this is a good idea. Thanks. :)
Great, and several others agree it's good idea too.
Pull requests are REALLY nice, mailing list works for simple stuff but get's
cluttered quickly. With pull requests, there's no need for multiple versions,
you just push and the pull request auto-updates. Also, you can do in-line code
comments which is really handy.
Opening issues is also SUPER easy. For yours and others benefit, I'll detail
the whole process on some wiki documentation.
I'll also open up a tracking issue for us and include that in the documentation.
Okay, here it is: https://github.com/autotest/autotest/issues/497
I'm just starting the workflow documentation now, but it'll be based on:
https://www.redhat.com/archives/autotest-kernel/2012-July/msg00084.html
I'd suggest we not bother with anything currently "in process", meaning
items already submitted to the mailing list. Let's just use this for
new stuff, i.e. the next set of new tests.
Also, no need to create issues/pull-requests for the whole list of
tests. Just as they come to mind and/or as you're beginning work on
them. If you have trouble assigning issues to yourself, just let me,
lmr, or cleber know and we'll take care of it.
Thanks.
--
Chris Evich, RHCA, RHCE, RHCDS, RHCSS
Quality Assurance Engineer
e-mail: cevich + `@' + redhat.com o: 1-888-RED-HAT1 x44214
_______________________________________________
Autotest-kernel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/autotest-kernel
