From: Brian Beattie <beattie@beattie-home.net>
To: buildroot@busybox.net
Subject: [Buildroot] at91 board patches
Date: Thu, 26 Jun 2008 07:24:09 -0700 [thread overview]
Message-ID: <1214490249.6242.68.camel@kokopelli> (raw)
I don't know if anybody has had chance to look at my patches or what I
could do to move the process along. I'm tempted to try and get svn
access but I don't think I've done anything to qualify for it yet.
If there is anything I can do to support the process of getting my
patches into svn let me know.
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting a bad thing?
Brian Beattie LFS12947 | "Honor isn't about making the right choices.
beattie at beattie-home.net | It's about dealing with the consequences."
www.beattie-home.net | -- Midori Koto
reply other threads:[~2008-06-26 14:24 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=1214490249.6242.68.camel@kokopelli \
--to=beattie@beattie-home.net \
--cc=buildroot@busybox.net \
/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