From: Jonathan Cameron <jic23@cam.ac.uk>
To: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: iio temporary? github tree.
Date: Tue, 20 Sep 2011 10:39:46 +0100 [thread overview]
Message-ID: <4E785F62.9010603@cam.ac.uk> (raw)
I've joined the crowd.
my iio-blue tree is available for now at:
https://github.com/jic23/linux-iio
Status is the same - I will rebase + randomly mess with the
history of anything I haven't already sent on to Greg.
Basically it will continue to eat babies for now.
Jonathan
p.s. I'm rather liking the github interface.
reply other threads:[~2011-09-20 9:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4E785F62.9010603@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).