From: Jonathan Cameron <jic23@kernel.org>
To: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: IIO new flow for patches into kernel.
Date: Sat, 30 Jun 2012 13:38:39 +0100 [thread overview]
Message-ID: <4FEEF34F.8060507@kernel.org> (raw)
Hi All,
At Greg's suggestion I'm moving to a more conventional
work flow. Hence I'll merge patches that I am happy with
Sign-off on them etc and send pull requests to Greg.
I think I've just sent everything that was ready to go
that Greg hasn't already merged, but if anything fell
through the cracks please do point it out to me!
For reference my tree is at:
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
the branches that matter are
fixes-togreg. Stuff for the current cycle.
togreg. New stuff for the next cycle.
Jonathan
reply other threads:[~2012-06-30 12:38 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=4FEEF34F.8060507@kernel.org \
--to=jic23@kernel.org \
--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).