[U-Boot-Users] Merge Window Closed.

[U-Boot-Users] Merge Window Closed.

[Wolfgang Denk]

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

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

[U-Boot-Users] Merge Window Closed.

[Dirk Behme]

Wolfgang Denk wrote:
> 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

[U-Boot-Users] Merge Window Closed.

[ksi at koi8.net]

On Sun, 19 Aug 2007, Dirk Behme wrote:

> Wolfgang Denk wrote:
>> 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.   *
******************************************************************

[U-Boot-Users] Merge Window Closed.

[Dirk Behme]

ksi at koi8.net wrote:
> On Sun, 19 Aug 2007, Dirk Behme wrote:
> 
>> Wolfgang Denk wrote:
>>
>>> 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

[U-Boot-Users] Merge Window Closed.

[Wolfgang Denk]

In message <46D2FEB0.6090900@googlemail.com> 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

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

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

[Jerry Van Baren]

Wolfgang Denk wrote:
> In message <46D2FEB0.6090900@googlemail.com> 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

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

[Ben Warren]

Jerry Van Baren wrote:
> Wolfgang Denk wrote:
>   
>> In message <46D2FEB0.6090900@googlemail.com> 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>

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

Ben

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

[Wolfgang Denk]

Hello,

in message <46D588E6.3020209@smiths-aerospace.com> 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.

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

> 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 ;-)

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

> 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" :-)

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

> 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

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

[U-Boot-Users] Merge Window Closed.

[Michal Simek]

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" <wd@denx.de>
To: <u-boot-users@lists.sourceforge.net>
Sent: Sunday, August 19, 2007 2:13 PM
Subject: [U-Boot-Users] Merge Window Closed.


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


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


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


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


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

[U-Boot-Users] Merge Window Closed.

[Jon Loeliger]

On Wed, 2007-08-29 at 13:21, Michal Simek 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.
> 
> 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

[U-Boot-Users] Merge Window Closed.

[Wolfgang Denk]

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?

> 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

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

[U-Boot-Users] Merge Window Closed.

[Michal Simek]

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

[U-Boot-Users] Merge Window Closed.

[Wolfgang Denk]

Dear Michal,

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

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