From: Ian Campbell <ijc@hellion.org.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] Requesting a custodian tree for sunxi (Allwinner) maintenance
Date: Wed, 02 Jul 2014 18:57:28 +0100 [thread overview]
Message-ID: <1404323848.28016.29.camel@dagon.hellion.org.uk> (raw)
Hi,
Hans and I would like to propose the creation of a uboot-sunxi.git
custodian tree for things relating to the Allwinner platforms. It would
be a downstream of uboot-arm.git tree with responsibility for it shared
between us. This was previously mentioned on list[0] but we figured it
deserved it's own thread.
I have attached the public half of a fresh ssh key generated for this
purpose. Hans, you should follow up with yours.
Thanks,
Ian.
[0] http://lists.denx.de/pipermail/u-boot/2014-June/182701.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: id_rsa_uboot.pub
Type: application/vnd.ms-publisher
Size: 391 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140702/65d6bb04/attachment.bin>
next reply other threads:[~2014-07-02 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 17:57 Ian Campbell [this message]
2014-07-03 14:15 ` [U-Boot] Requesting a custodian tree for sunxi (Allwinner) maintenance Detlev Zundel
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=1404323848.28016.29.camel@dagon.hellion.org.uk \
--to=ijc@hellion.org.uk \
--cc=u-boot@lists.denx.de \
/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