From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9256] [Config file] New device: Odroid-U2/U3
Date: Wed, 26 Oct 2016 07:36:18 +0000 [thread overview]
Message-ID: <bug-9256-163-BogJC3pr3T@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9256-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9256
--- Comment #2 from Wesley Chan <qlb1234@gmail.com> ---
Dear Thomas,
Thank you for your suggestion. However, I decided I don't want to submit the
patch to the mailing list for the following reasons:
1. I was subscribed to the mailing list in before and sent my config file. Not
only no one has replied, I got tons of mails discussing all kinds of bugs that
I don't care.
2. I don't want to be disrespectful and put a fake e-mail address on the commit
history, yet I don't want my real e-mail address on it.
3. I can follow the instructions to create a patch but I have zero experience
about the Buildroot project, so I'm afraid I won't be providing a patch with
100% correctness on the format your team demands. I don't want to go back and
forth for a tiny enhancement.
I still want to contribute, but not in an engaged way. I think it's the best
for me to just leave the config file and readme.txt here. Please tell me if
your team still wants it. Thanks.
Regards,
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2016-10-26 7:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-18 1:58 [Buildroot] [Bug 9256] New: [Config file] New device: Odroid-U2/U3 bugzilla at busybox.net
2016-10-23 12:57 ` [Buildroot] [Bug 9256] " bugzilla at busybox.net
2016-10-26 7:36 ` bugzilla at busybox.net [this message]
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=bug-9256-163-BogJC3pr3T@https.bugs.busybox.net/ \
--to=bugzilla@busybox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.