From: Gaute Hope <eg@gaute.vetsj.com>
To: "Martin Bähr" <mbaehr@email.archlab.tuwien.ac.at>
Cc: supmua <supmua@googlegroups.com>
Subject: Re: [sup] papercuts and google code-in
Date: Sun, 28 Dec 2014 17:06:10 +0000 [thread overview]
Message-ID: <1419786092-astroid-5-92dov2kfj7-1194@strange> (raw)
In-Reply-To: <1419782945-sup-3956@email.archlab.tuwien.ac.at>
Excerpts from Martin Bähr's message of December 28, 2014 17:12:
> Excerpts from Gaute Hope's message of 2014-12-28 15:14:01 +0100:
>> I invited you to become a contributor to the sup organization on github
>> (embee right?). That way you can assign yourself to these issues and
>> handle them on the issue-tracker.
>>
>> Thanks for doing this, I hope there is time to polish things up enough
>> to merge them.
>
> i hope so too.
> though i'd appreciate a little help in reviewing pull-requests, at least in
> terms of deciding whether they are good enough for merging. in particular i am
> inexperienced in dealing with test-cases, and it would be nice if you could
> indicate if an issue should have a test case or not. or point out what to test for.
Yep, I can probably help a bit out there - though my time is limited.
Make sure that the code is tested by both the author and at least one
other (you?). E.g. #358 is difficult to write a test case for, but you
need to test how it works with:
- no .sup dir
- a previous config.yml but no sources.yml
- both existing, but perhaps sources empty.
indicate in the PR if you have tested it and what your recommendation is.
#357 does not need a test case, but I am not sure it is more accurate
now than before - please see my comment there.
cheers, gaute
next prev parent reply other threads:[~2014-12-28 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-27 18:05 Martin Bähr
2014-12-28 14:14 ` [sup] " Gaute Hope
2014-12-28 16:12 ` Martin Bähr
2014-12-28 17:06 ` Gaute Hope [this message]
2014-12-28 17:31 ` Martin Bähr
2014-12-28 18:00 ` Gaute Hope
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1419786092-astroid-5-92dov2kfj7-1194@strange \
--to=eg@gaute.vetsj.com \
--cc=mbaehr@email.archlab.tuwien.ac.at \
--cc=supmua@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox