From: "Martin Bähr" <mbaehr@email.archlab.tuwien.ac.at>
To: Gaute Hope <eg@gaute.vetsj.com>
Cc: supmua <supmua@googlegroups.com>
Subject: Re: [sup] papercuts and google code-in
Date: Sun, 28 Dec 2014 17:12:07 +0100 [thread overview]
Message-ID: <1419782945-sup-3956@email.archlab.tuwien.ac.at> (raw)
In-Reply-To: <1419775872-astroid-4-gk0eja34lo-1194@strange>
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.
greetings, martin.
--
eKita - the online platform for your entire academic life
--
chief engineer eKita.co
pike programmer pike.lysator.liu.se caudium.net societyserver.org
BLUG secretary beijinglug.org
foresight developer foresightlinux.org realss.com
unix sysadmin
Martin Bähr working in china http://societyserver.org/mbaehr/
next prev parent reply other threads:[~2014-12-28 16:12 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 [this message]
2014-12-28 17:06 ` Gaute Hope
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=1419782945-sup-3956@email.archlab.tuwien.ac.at \
--to=mbaehr@email.archlab.tuwien.ac.at \
--cc=eg@gaute.vetsj.com \
--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