From: Graeme Russ <graeme.russ@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] x86: Anyone willing to take over the reigns
Date: Sun, 28 Oct 2012 22:44:22 +1100 [thread overview]
Message-ID: <508D1A96.9080107@gmail.com> (raw)
Hi All,
I think it's finally time I admitted that I simply have too much on my
plate and need to give a few things up. Work and family life have got to
the point where I can only manage to grab a quick hour here and there at my
desk at home and I simply do not have enough time (or energy) to keep
maintaining the x86 repo.
It's been really good to see the Chromium guys giving U-Boot x86 some much
needed love, but it has highlighted to me just how much work it has been
(and will be) to keep up. To give you an idea, I haven't sync'd my local
repo (much less built U-Boot) in over a month now. My bandwidth is down to
making a few passing comments on very specific patches.
Does anyone feel up to the task of taking on the x86 repo? If not, I'm sure
that it could revert to the old days of being directly managed as
'miscellaneous'
Regards,
Graeme
next reply other threads:[~2012-10-28 11:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-28 11:44 Graeme Russ [this message]
2012-10-30 16:21 ` [U-Boot] x86: Anyone willing to take over the reigns Simon Glass
2012-10-30 21:05 ` Graeme Russ
2012-10-30 21:21 ` Tom Rini
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=508D1A96.9080107@gmail.com \
--to=graeme.russ@gmail.com \
--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