From: Grant Likely <grant.likely@secretlab.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] make MAKEALL more immune to mergeconflicts
Date: Fri, 10 Aug 2007 09:40:39 -0600 [thread overview]
Message-ID: <fa686aa40708100840g6e35fc08ic9adbc355ed55cc0@mail.gmail.com> (raw)
In-Reply-To: <12068826.post@talk.nabble.com>
On 8/9/07, David Saada <David.Saada@ecitele.com> wrote:
> Furthermore, Wolfgang may disagree here, but I really think that only
> reference boards (i.e. boards needed for evaluation of processors etc.)
> should be merged into U-boot's main stream repository. Our boards are just
> variations of the Freescale reference boards, and I guess that's the same
> for many other boards by other companies. I wouldn't want to see ALL these
> boards merged into U-boot. Of course that if one finds a problem, or have an
> improvement, one's expected to send a patch to the proper place (as I did
> with the 83xx Makefile). Needless to say that the boards' code should be
> published due to GPL terms, but again - don't think it should be in the main
> U-boot repository.
I disagree. :-) I think you're opinions makes the assumption that
u-boot is a product. It is not; it is a process. What I mean here is
that our primary goal is to continually develop the best bootloader.
The exact set of boards that compiles out of the box is a secondary
objective. Your argument is that if it's not a generally available
board, then it is uninteresting. That viewpoint makes sense if you
view u-boot as a thing that you take, modify and ship (ie. a product
which you consume).
However, the u-boot project is about the *process* of developing the
end product. It involves understanding how u-boot is being used in
real-world scenarios. It involves recognizing patterns in the code
and consolidating on common patterns. We *NEED* real world board
ports to have a better understanding of how to improve u-boot. My
view is exactly the opposite; obscure boards are not uninteresting,
they are extremely interesting.
> If you agree with me, then my suggestion would spare you the pain of merging
> the names of your boards (again - the ones that are either not ready for
> upstream merging, or the ones that are not supposed to go to U-boot's repos)
> into MAKEALL.
> Best regards,
> David.
>
> --
> View this message in context: http://www.nabble.com/-PATCH--make-MAKEALL-more-immune-to-merge-conflicts-tf4227360.html#a12068826
> Sent from the Uboot - Users mailing list archive at Nabble.com.
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
>
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely at secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2007-08-10 15:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 0:06 [U-Boot-Users] [PATCH] make MAKEALL more immune to merge conflicts Kim Phillips
2007-08-07 6:48 ` Wolfgang Denk
2007-08-07 10:21 ` Stefan Roese
2007-08-07 10:30 ` [U-Boot-Users] [PATCH] make MAKEALL more immune to mergeconflicts Martin Krause
2007-08-08 12:39 ` David Saada
2007-08-08 15:43 ` Wolfgang Denk
2007-08-08 15:59 ` Jon Loeliger
2007-08-08 18:03 ` Wolfgang Denk
2007-08-09 8:55 ` David Saada
2007-08-10 15:40 ` Grant Likely [this message]
2007-08-10 15:56 ` Wolfgang Denk
2007-08-09 2:49 ` Timur Tabi
2007-08-08 16:50 ` [U-Boot-Users] [PATCH] make MAKEALL more immune to merge conflicts Detlev Zundel
2007-08-08 18:09 ` Wolfgang Denk
2007-08-10 7:54 ` Kim Phillips
2007-08-10 8:44 ` Wolfgang Denk
2007-08-07 16:23 ` Kim Phillips
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=fa686aa40708100840g6e35fc08ic9adbc355ed55cc0@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--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