public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] OMAP3 Regression after merging ARM relocation code for custom board
Date: Tue, 15 Mar 2011 22:59:41 +0100	[thread overview]
Message-ID: <20110315215941.63841151F7D@gemini.denx.de> (raw)
In-Reply-To: <4D7FDD06.5080009@lucaceresoli.net>

Dear Luca Ceresoli,

In message <4D7FDD06.5080009@lucaceresoli.net> you wrote:
> 
> Nevertheless, the board will never be publicly available unless one buys 
> a quite expensive product, and I don't think detailed hardware 
> specifications will ever be available (this definitely does not depend 
> on me...). It's a product, not a development board or similar.

This really doesn't matter at all in regards of wether you can push
your code upstream to have it maintained with the rest of the mainline
code.

> Do you think it would be feasible to give support even with such 
> restrictions, if the software were publicly available?

I'm not talking about "publicly available".  I'm talking about coe
that has been merged into the mainline U-Boot distribution. That's the
only code that gets free community support.

> Pardon the question, I'm just trying to understand how the U-boot 
> community does things as I'm pretty new here.

It works like other, similar communites, too.  Take Linux for example.


> Merging little pieces at a time was my "divide et impera" approach to 
> merge ~1 year of upstream history without facing a huge mountain of 
> merge conflicts, compilation issues and runtime failures all at a time 
> on a codebase that I'm not familiar with. On one hand, it allowed me to 
> learn a bit about U-boot, but I understand it makes it difficult to 
> obtain support.

Such an approach is painful.  Learn a lesson from it.  Sync against
mainline frequently, eventually even on a daily base, or at least
every few days.  Use tools (git - like pulling mainline into your
repository, or maintaining your code in a brnch that you rebase
against mainline).

> I'll try the other way around with a big merge-all.

No.  Create a branch, and try to rebase your branch.


Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Good manners are the settled  medium  of  social,  as  specie  is  of
commercial, life; returns are equally expected for both.
           - Lord Chesterfield _Letters to his Son_, 25 December 1753

  reply	other threads:[~2011-03-15 21:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15 16:46 [U-Boot] OMAP3 Regression after merging ARM relocation code for custom board Luca Ceresoli
2011-03-15 19:07 ` Wolfgang Denk
2011-03-15 21:41   ` Luca Ceresoli
2011-03-15 21:59     ` Wolfgang Denk [this message]
2011-03-15 19:16 ` Albert ARIBAUD
  -- strict thread matches above, loose matches on Subject: below --
2011-03-21 11:42 Luca Ceresoli

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=20110315215941.63841151F7D@gemini.denx.de \
    --to=wd@denx.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