From: Alexander Holler <holler@ahsoftware.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] omap3_beagle: enable the use of a plain text file named uEnv.txt instead of boot.scr
Date: Wed, 02 Mar 2011 20:55:54 +0100 [thread overview]
Message-ID: <4D6EA0CA.1030604@ahsoftware.de> (raw)
In-Reply-To: <4D6E82A9.4000400@ahsoftware.de>
Hello,
just a last word. I don't have to decide which patch is used and I don't
have any problem if v2 is used. I'm able to modify bootcmd like I wish
and can live with any version.
I've justed wanted to make clear why I haven't used a simpler approach.
Anyway, if v2 will be used, please just remove my name as author, I
don't want to be responsible for the possible arising confusion.
Everyone can still use as much from that patch as he wishes, please just
don't use my name as author for a modified patch with a changed logic. ;)
Regards,
Alexander
next prev parent reply other threads:[~2011-03-02 19:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 23:08 [U-Boot] [PATCH] omap3_beagle: enable the use of a plain text file named uEnv.txt instead of boot.scr Alexander Holler
2011-02-04 17:41 ` Jason Kridner
2011-03-01 23:37 ` [U-Boot] [PATCH v2] " Jason Kridner
2011-03-02 2:54 ` Alexander Holler
2011-03-02 15:44 ` Jason Kridner
2011-03-02 17:47 ` Alexander Holler
2011-03-02 19:55 ` Alexander Holler [this message]
2011-03-02 20:26 ` [U-Boot] [PATCH v3] " Jason Kridner
2011-03-02 23:41 ` Alexander Holler
2011-03-02 23:48 ` [U-Boot] [beagleboard] " Robert Nelson
2011-03-03 15:04 ` Jason Kridner
2011-03-04 1:30 ` Alexander Holler
2011-03-04 1:43 ` [U-Boot] " Alexander Holler
2011-03-04 1:51 ` Robert Nelson
2011-03-03 15:08 ` [U-Boot] [PATCH v4] " Jason Kridner
2011-03-05 12:31 ` Alexander Holler
2011-03-05 12:50 ` Alexander Holler
2011-03-13 21:26 ` Wolfgang Denk
2011-04-18 21:35 ` [U-Boot] [PATCH v3] " Paulraj, Sandeep
2011-04-18 23:01 ` Wolfgang Denk
2011-04-18 23:32 ` Paulraj, Sandeep
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=4D6EA0CA.1030604@ahsoftware.de \
--to=holler@ahsoftware.de \
--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