From: Hamish D <dmishd@gmail.com>
To: Gaute Hope <eg@gaute.vetsj.com>
Cc: Matthieu Rakotojaona <matthieu.rakotojaona@gmail.com>,
sup-talk <sup-talk@rubyforge.org>,
sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-talk] Github organization for sup and heliotrope
Date: Thu, 17 Jan 2013 23:43:01 +0000 [thread overview]
Message-ID: <CAOxvSbd=VBvhC6YMN+xEJDj3Jk2rfVEv5HkdUv1_ufrrA96CeA@mail.gmail.com> (raw)
In-Reply-To: <CAOxvSbctHrgaVXcpLVzasxKo8B+qLP6PCNLJBb2=YDFc5HObWA@mail.gmail.com>
> Right, should probably go and dig up various patches I've copied off
> the email list that I wasn't sure about and turn them into pull
> requests to open up discussion on them.
I've started doing that with 4 well formatted patches I wasn't
entirely sure about (3 from Gaute) and put my comments on those pull
requests. If I get good answers we can merge them.
Got a few more diffs I'll have to get to another night.
Hamish
next prev parent reply other threads:[~2013-01-17 23:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 20:15 Matthieu Rakotojaona
2013-01-17 20:52 ` Gaute Hope
2013-01-17 21:09 ` Hamish D
2013-01-17 23:43 ` Hamish D [this message]
2013-01-17 23:01 ` [sup-devel] " Hamish D
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='CAOxvSbd=VBvhC6YMN+xEJDj3Jk2rfVEv5HkdUv1_ufrrA96CeA@mail.gmail.com' \
--to=dmishd@gmail.com \
--cc=eg@gaute.vetsj.com \
--cc=matthieu.rakotojaona@gmail.com \
--cc=sup-devel@rubyforge.org \
--cc=sup-talk@rubyforge.org \
/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