From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Makefile suggestion
Date: Thu, 24 Aug 2006 00:07:29 +0200 [thread overview]
Message-ID: <20060823220729.9143535360D@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 23 Aug 2006 22:21:54 +0200." <008f01c6c6f2$1b58fd80$8f4765d5@atmel.com>
In message <008f01c6c6f2$1b58fd80$8f4765d5@atmel.com> you wrote:
>
> The U-boot Makefile is quite large and growing.
> I have seen problem where a new patch breaks because another patch has been applied
> between the checkout of the source dir and the acceptance of the patch.
> ("avr32" board support breaks on "blackfin")
These are normal merge conflicts, and usually trivial to resolve.
> The main function of the proposed patch is to add:
> "include board/*/board.mk"
> to the toplevel Makefile right before the mkconfig's start
Rejected. I really want to be able to see everythin in one place and
file. This may become a long file, but then you know exactly where to
search.
Not so long ago you could run "grep foo Documentation/Configure.help"
in the Linux kernel tree to find out what config option "foo" was
about. Try this in a current Linux kernel tree with it's zillions of
scattered Kconfig files (including all the Kconfig.char,
Kconfig.debug, Kconfig.i386, Kconfig.net, Kconfig.scsi,
Kconfig.x86_64 and what else variants).
Please don't worry about such merge conflicts in the Makefile - I
never complaint about such merge conflicts when adding patches.
> This is the first patch I send, if I have made any glaring mistakes,
> I will try to improve based on feedback.
I reject this patch because it tries to fix a poroblem which does not
exist, and instead it makes the code much harder to maintain.
> diff -purN u-boot-1.1.4-0rig/board/template/board.mk > u-boot-1.1.4/board/template/board.mk
> --- u-boot-1.1.4-0rig/board/template/board.mk 1970-01-01 > 01:00:00.000000000 +0100
> +++ u-boot-1.1.4/board/template/board.mk 2006-08-23 21:50:30.000000000 > +0200
Why don't you use git?
> +include board/*/board.mk
BTW: this approach is broken. It does not handle the case of vendor
directories like board/amcc/, board/esd/, etc.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"The more data I punch in this card, the lighter it becomes, and the
lower the mailing cost."
- Stan Kelly-Bootle, "The Devil's DP Dictionary"
next prev parent reply other threads:[~2006-08-23 22:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 9:45 [U-Boot-Users] Submitting Patch at sourceforge fails Ulf Samuelsson
2006-08-22 10:25 ` Wolfgang Denk
2006-08-22 13:52 ` Ulf Samuelsson
2006-08-22 15:38 ` Wolfgang Denk
2006-08-22 19:02 ` Ulf Samuelsson
2006-08-22 19:02 ` Ulf Samuelsson
2006-08-22 20:26 ` Wolfgang Denk
2006-08-23 15:03 ` Andreas Schweigstill
2006-08-23 15:23 ` Jeff Mock
2006-08-23 16:44 ` [U-Boot-Users] Off-topic: Serial port redirection Andreas Schweigstill
2006-08-23 19:35 ` Wolfgang Denk
2006-08-23 19:48 ` Jerry Van Baren
2006-08-23 20:45 ` [U-Boot-Users] Submitting Patch at sourceforge fails Ulf Samuelsson
2006-08-23 22:25 ` Wolfgang Denk
2006-08-23 20:21 ` [U-Boot-Users] Makefile suggestion Ulf Samuelsson
2006-08-23 22:07 ` Wolfgang Denk [this message]
2006-08-24 7:53 ` Ulf Samuelsson
2006-08-24 9:29 ` Wolfgang Denk
2006-08-23 8:06 ` [U-Boot-Users] Submitting Patch at sourceforge fails Stefan Roese
2006-08-23 8:13 ` Ulf Samuelsson
2006-08-23 9:46 ` Stefan Roese
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=20060823220729.9143535360D@atlas.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