Skip to contentSkip to conversation

Merge Window Closed.

U-Boot-Users Wolfgang Denk 7 participants 13 messages Aug 19, 2007 – Sep 11, 2007

lore
Share & tools
lore
#0 lore raw

Hi everybody.

our first merge window has just ended. I think I have processed all pull requests and added all (recent) open patches. Please have a look and check if anything that should go into the next release and has been submitted before the deadline is still missing.

Please find attached below the build errors resulting when running the "MAKEALL" script for the "arm", "mips" and "ppc" architectures. I used the ELDk 4.1 tool chain to do this, just in case it matters.

* Please help testing by running MAKEALL for the other architectures for which I don't have tools and boards to test...

* Board maintainers: please help clean up build errors on warnings on your boards.

Please help testing and fixing so we can have a high quality code release at the end of this cycle.

BTW: what should the next release be named - 1.2.1 or 1.3.0 ?

Best regards,

Wolfgang Denk

Signature · 27 lines
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
Faith may be defined briefly as an illogical belief in the  occurence
of the improbable.                                    - H. L. Mencken

-------------- next part --------------
A non-text attachment was scrubbed...
Name: arm-errors.tar.gz
Type: application/x-gzip
Size: 3811 bytes
Desc: arm-errors.tar.gz
Url : http://lists.denx.de/pipermail/u-boot/attachments/20070819/6468e4e4/attachment.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mips-errors.tar.gz
Type: application/x-gzip
Size: 1006 bytes
Desc: mips-errors.tar.gz
Url : http://lists.denx.de/pipermail/u-boot/attachments/20070819/6468e4e4/attachment-0001.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ppc-errors.tar.gz
Type: application/x-gzip
Size: 2514 bytes
Desc: ppc-errors.tar.gz
Url : http://lists.denx.de/pipermail/u-boot/attachments/20070819/6468e4e4/attachment-0002.bin 
#1 lore raw
Quoted 1 line · Wolfgang Denk

BTW: what should the next release be named - 1.2.1 or 1.3.0 ?

A lot of updates and fixes, new merge strategy, I vote for 1.3.0.

Best regards

Dirk

#2 lore raw
Quoted 4 lines · Dirk Behme
Quoted 1 line · Wolfgang Denk

BTW: what should the next release be named - 1.2.1 or 1.3.0 ?

A lot of updates and fixes, new merge strategy, I vote for 1.3.0.

Me too :)

---
******************************************************************
* KSI at home KOI8 Net < > The impossible we do immediately. *
* Las Vegas NV, USA < > Miracles require 24-hour notice. *
******************************************************************

#3 lore raw
Quoted 11 lines · ksi at koi8.net wrote:
Quoted 6 lines · Dirk Behme
Quoted 1 line · Wolfgang Denk

BTW: what should the next release be named - 1.2.1 or 1.3.0 ?

A lot of updates and fixes, new merge strategy, I vote for 1.3.0.

Me too :)

What's about a u-boot-1.3.0-rc1 tag in git and a
u-boot-1.3.0-rc1.tar.bz2 on ftp server?

Cheers

Dirk

#4 lore raw
Quoted 3 lines · In message <[email protected]> you wrote:

What's about a u-boot-1.3.0-rc1 tag in git and a
u-boot-1.3.0-rc1.tar.bz2 on ftp server?

Will do that. But I want to integrate the first round of feedback first. There are way too many show-stopper bugs in the current code to call it a release candidate. If I just had a little more time...

Best regards,

Wolfgang Denk

Signature · 7 lines
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
Es ist offensichtlich, dass das menschliche Gehirn wie  ein  Computer
funktioniert.  Da  es  keine  dummen Computer gibt, gibt es also auch
keine dummen Menschen. Nur ein paar Leute, die unter DOS laufen.
                                                       -- <unbekannt>
#5 lore raw

[U-Boot-Users] Release numbering (was Merge Window Closed.)

Quoted 11 lines · Wolfgang Denk
Quoted 2 lines · In message <[email protected]> you wrote:

What's about a u-boot-1.3.0-rc1 tag in git and a
u-boot-1.3.0-rc1.tar.bz2 on ftp server?

Will do that. But I want to integrate the first round of feedback first. There are way too many show-stopper bugs in the current code to call it a release candidate. If I just had a little more time...

Best regards,

Wolfgang Denk

What about adopting Ubuntu's philosophy and numbering by year and month Y.M?
<http://www.ubuntu.com/aboutus/faq>

This has the disadvantage of not clearly marking major changes
(discontinuities) e.g. 1.x -> 2.0 or 1.2.y -> 1.3.0. Assuming there
are no earth-shattering discontinuities in the future, that isn't a problem. I'm not sure we are "there" yet, but u-boot has been around and refined for quite some time now and the changes have become a lot more incremental (or maybe I've just become more comfortable with it?).

On the "advantages" side...

1) It acknowledges that u-boot (as with most open source projects) is subject to continuous rolling improvement.

2) It eliminates the debate of whether the major or just the minor number needs to be rolled.

3) When someone says "my build based on version 7.8 is broken" we can scale our scorn based on how old the release is without having to look it up. ;-)

4) This is also in line with Linus's current philosophy that the kernel will be 2.6.xxxxxx forever. (I suspect this won't hold literally true forever, I predict the "2.6" prefix will eventually be dropped.)

Going to date-based numbering makes a lot of sense to me.

Best regards,
gvb

#6 lore raw

[U-Boot-Users] Release numbering (was Merge Window Closed.)

Quoted 11 lines · Jerry Van Baren
Quoted 9 lines · Wolfgang Denk
Quoted 3 lines · In message <[email protected]> you wrote:

What's about a u-boot-1.3.0-rc1 tag in git and a
u-boot-1.3.0-rc1.tar.bz2 on ftp server?

Will do that. But I want to integrate the first round of feedback first. There are way too many show-stopper bugs in the current code to call it a release candidate. If I just had a little more time...

Quoted 7 lines
Quoted 4 lines

Best regards,

Wolfgang Denk

What about adopting Ubuntu's philosophy and numbering by year and month Y.M?
<http://www.ubuntu.com/aboutus/faq>

Great idea, but who's going to come up with the silly animal names?

Ben

#7 lore raw

[U-Boot-Users] Release numbering (was Merge Window Closed.)

In reply to Jerry Van Baren

Hello,

Quoted 3 lines · in message <[email protected]> you wrote:

What about adopting Ubuntu's philosophy and numbering by year and month Y.M?
<http://www.ubuntu.com/aboutus/faq>

To be honest: I don't like it. No rational reason, just gut feeling.

Quoted 3 lines

This has the disadvantage of not clearly marking major changes
(discontinuities) e.g. 1.x -> 2.0 or 1.2.y -> 1.3.0. Assuming there
are no earth-shattering discontinuities in the future, that isn't a

There will be such things, I guess... 2.0 is already in a repo...

Quoted 2 lines

1) It acknowledges that u-boot (as with most open source projects) is subject to continuous rolling improvement.

Oops? I don't see any difference for this between onve versioning scheme and any other, as long as the versions change frequently ;-)

Quoted 2 lines

2) It eliminates the debate of whether the major or just the minor number needs to be rolled.

ACK. But actually this is more a disadvantage - see above.

Quoted 3 lines

3) When someone says "my build based on version 7.8 is broken" we can scale our scorn based on how old the release is without having to look it up. ;-)

I never look this up. Anything that is not TOT is "too old" :-)

Quoted 3 lines

4) This is also in line with Linus's current philosophy that the kernel will be 2.6.xxxxxx forever. (I suspect this won't hold literally true forever, I predict the "2.6" prefix will eventually be dropped.)

Ummm... but Linux does NOT use da date based version number.

Quoted 1 line

Going to date-based numbering makes a lot of sense to me.

I feel this is mostly a matter of taste.

I have been using date based labels all the time when U-Boot was still in CVS (see all the LABEL_200y_mm_dd_HHMM tags we have). And I must say that I really got sick of this. It served a specific need in CVS, but I never needed this again in git. If it was not for a public release process I wouln't need any version number at all. But whatever we may use, please not date based stamps. I think they are *stupid*. JUst my 0.02 EUR.

Best regards,

Wolfgang Denk

Signature · 7 lines
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
The White Rabbit put on his spectacles. "Where shall I begin,  please
your Majesty ?" he asked.
"Begin at the beginning,", the King said, very gravely,  "and  go  on
till you come to the end: then stop."                -- Lewis Carroll
#8 lore raw
In reply to Wolfgang Denk

Hi Wolfgang,

Microblaze source code in main tree have problems due to redesigning commands
handling. I fixed this in microblaze branch.

I sent some patches to discuss but I have no response on it. ROMFS, EmacLite and Emac.

Shall I send patches again?
Or you can pull them from microblaze branch.

Best regards,
Michal Simek

----- Original Message -----
From: "Wolfgang Denk" <[email protected]>
To: <[email protected]>
Sent: Sunday, August 19, 2007 2:13 PM
Subject: [U-Boot-Users] Merge Window Closed.

Quoted 18 lines

Hi everybody.

our first merge window has just ended. I think I have processed all pull requests and added all (recent) open patches. Please have a look and check if anything that should go into the next release and has been submitted before the deadline is still missing.

Please find attached below the build errors resulting when running the "MAKEALL" script for the "arm", "mips" and "ppc" architectures. I used the ELDk 4.1 tool chain to do this, just in case it matters.

* Please help testing by running MAKEALL for the other architectures for which I don't have tools and boards to test...

* Board maintainers: please help clean up build errors on warnings on your boards.

Quoted 17 lines

Please help testing and fixing so we can have a high quality code release at the end of this cycle.

BTW: what should the next release be named - 1.2.1 or 1.3.0 ?

Best regards,

Wolfgang Denk

Signature · 5 lines
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
Faith may be defined briefly as an illogical belief in the  occurence
of the improbable.                                    - H. L. Mencken

--------------------------------------------------------------------------------

Quoted 5 lines

-------------------------------------------------------------------------
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/

--------------------------------------------------------------------------------

Quoted 5 lines

_______________________________________________
U-Boot-Users mailing list
U-Boot-Users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users

--------------------------------------------------------------------------------

No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.484 / Virus Database: 269.11.19/955 - Release Date: 15.8.2007 04:55

#9 lore raw
Quoted 6 lines · Michal Simek

Hi Wolfgang,

Microblaze source code in main tree have problems due to redesigning commands
handling. I fixed this in microblaze branch.

Quoted 8 lines

I sent some patches to discuss but I have no response on it. ROMFS, EmacLite and Emac.

Shall I send patches again?
Or you can pull them from microblaze branch.

Best regards,
Michal Simek

Hi Michal,

Please repost your patch series. As I recall, there were several issues with your patch series that needed to be cleaned up before they could be pulled.

Thanks,
jdl

#10 lore raw
In reply to Michal Simek
Quoted 4 lines · In message <007101c7ea69$7cf1b730$5d722093@monstrone> you wrote:

Microblaze source code in main tree have problems due to redesigning commands
handling. I fixed this in microblaze branch.

Which specific patches / commits are you talking about?

Quoted 5 lines

I sent some patches to discuss but I have no response on it. ROMFS, EmacLite and Emac.

Shall I send patches again?
Or you can pull them from microblaze branch.

Sorry, I'd like to understand which specific commits you refer to.

Best regards,

Wolfgang Denk

Signature · 4 lines
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
F u cn rd ths u cnt spl wrth a dm!
#11 lore raw
Quoted 4 lines
Quoted 3 lines

Microblaze source code in main tree have problems due to redesigning commands
handling. I fixed this in microblaze branch.

Which specific patches / commits are you talking about?

I am talking about configs file in include/configs folder. I will send all patches again.

Best regards,
Michal Simek

#12 lore raw
In reply to Michal Simek

Dear Michal,

Quoted 11 lines · in message <007101c7ea69$7cf1b730$5d722093@monstrone> you wrote:

Hi Wolfgang,

Microblaze source code in main tree have problems due to redesigning commands
handling. I fixed this in microblaze branch.

I sent some patches to discuss but I have no response on it. ROMFS, EmacLite and Emac.

Shall I send patches again?
Or you can pull them from microblaze branch.

Just for the record: this is the only message I received from you that talks at all about pulling "from microblaze branch" (without saying exactly what this is and what it contains). You sent this on Wed, 29 Aug 2007 20:21:59, after the merge window was closed.

I did not - and do not - interpret this message as a pull request. I read this as a request to review patches.

If you want to send a pull request, you have to make this clear to me, like by following the docs in
http://www.denx.de/wiki/UBoot/CustodianGitTrees

Best regards,

Wolfgang Denk

Signature · 5 lines
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
You can't evaluate a man by logic alone.
	-- McCoy, "I, Mudd", stardate 4513.3