ATTENTION: Uu-boot-arm/master branch ROLLBACK to 28e5ac2d

U-Boot Albert ARIBAUD 3 participants 5 messages Oct 12, 2012

lore

Share & tools

lore

Albert ARIBAUD

author

2012-10-12 05:53 UTC #0 lore raw

Hi all,

I am sending this notice because I have force-pushed a rollback of u-boot-arm/master.

This is due to the recently submitted u-boot-arm/master pull request being NAKed by Tom: the content of this pull req was exactly that of the latest u-boot-samsung/master pull req and was a fast forward from previous u-boot-arm/master (28e5ac2d) which had received extensive testing from Tom.

Therefore, as a roll back of u-boot-arm/master was both easy to perform and safe(r) from a release perspective, I decided to stray from formal master branch management rules and force it back to 28e5ac2d.

All: if you intend to send a pull request to u-boot-arm/master, please rework this request to take this rollback into account.

Minkyu: for the reasons above, I suggest you roll u-boot-samsung/master back to 28e5ac2d before building and sending an amended pull req, but of course the choice is yours.

Amicalement,

Signature · 1 line

Albert.

Minkyu Kang

2012-10-12 06:39 UTC #1 lore raw

Dear Albert,

Quoted 15 lines · Albert ARIBAUD

Hi all,
I am sending this notice because I have force-pushed a rollback of u-boot-arm/master.
This is due to the recently submitted u-boot-arm/master pull request being NAKed by Tom: the content of this pull req was exactly that of the latest u-boot-samsung/master pull req and was a fast forward from previous u-boot-arm/master (28e5ac2d) which had received extensive testing from Tom.
Therefore, as a roll back of u-boot-arm/master was both easy to perform and safe(r) from a release perspective, I decided to stray from formal master branch management rules and force it back to 28e5ac2d.

Quoted 7 lines

All: if you intend to send a pull request to u-boot-arm/master, please rework this request to take this rollback into account.
Minkyu: for the reasons above, I suggest you roll u-boot-samsung/master back to 28e5ac2d before building and sending an amended pull req, but of course the choice is yours.

OK. I'll revert soft i2c patches and send new pull request at next Monday. Is it OK?

Thanks.
Minkyu Kang.

Signature · 2 lines

from. prom.
www.promsoft.net

Minkyu Kang

2012-10-12 06:45 UTC #2 lore raw

Quoted 21 lines · Minkyu Kang

Dear Albert,
Quoted 18 lines · Albert ARIBAUD
Hi all,
I am sending this notice because I have force-pushed a rollback of u-boot-arm/master.
This is due to the recently submitted u-boot-arm/master pull request being NAKed by Tom: the content of this pull req was exactly that of the latest u-boot-samsung/master pull req and was a fast forward from previous u-boot-arm/master (28e5ac2d) which had received extensive testing from Tom.
Therefore, as a roll back of u-boot-arm/master was both easy to perform and safe(r) from a release perspective, I decided to stray from formal master branch management rules and force it back to 28e5ac2d.
All: if you intend to send a pull request to u-boot-arm/master, please rework this request to take this rollback into account.

Quoted 6 lines

Quoted 4 lines
Minkyu: for the reasons above, I suggest you roll u-boot-samsung/master back to 28e5ac2d before building and sending an amended pull req, but of course the choice is yours.
OK. I'll revert soft i2c patches and send new pull request at next Monday.

sorry. spi, not i2c.

Quoted 1 line

Is it OK?

Signature · 2 lines

from. prom.
www.promsoft.net

Albert ARIBAUD

author

2012-10-12 10:00 UTC #3 lore raw

Hi Minkyu,

Quoted 22 lines · Minkyu Kang

Quoted 21 lines · Minkyu Kang
Dear Albert,
Quoted 18 lines · Albert ARIBAUD
Hi all,
I am sending this notice because I have force-pushed a rollback of u-boot-arm/master.
This is due to the recently submitted u-boot-arm/master pull request being NAKed by Tom: the content of this pull req was exactly that of the latest u-boot-samsung/master pull req and was a fast forward from previous u-boot-arm/master (28e5ac2d) which had received extensive testing from Tom.
Therefore, as a roll back of u-boot-arm/master was both easy to perform and safe(r) from a release perspective, I decided to stray from formal master branch management rules and force it back to 28e5ac2d.
All: if you intend to send a pull request to u-boot-arm/master, please rework this request to take this rollback into account.

Quoted 10 lines

Quoted 6 lines
Quoted 4 lines
Minkyu: for the reasons above, I suggest you roll u-boot-samsung/master back to 28e5ac2d before building and sending an amended pull req, but of course the choice is yours.
OK. I'll revert soft i2c patches and send new pull request at next Monday.
sorry. spi, not i2c.
Quoted 1 line
Is it OK?

It's ok, but note that it won't be included in the 2012.10 release anyway, as monday is the release date.

Amicalement,

Signature · 1 line

Albert.

Tom Rini

2012-10-12 14:33 UTC #4 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 40 lines · Albert ARIBAUD

Hi Minkyu,
Quoted 35 lines · Minkyu Kang
Quoted 32 lines · Minkyu Kang
Dear Albert,
Quoted 16 lines · Albert ARIBAUD
Hi all,
I am sending this notice because I have force-pushed a rollback of u-boot-arm/master.
This is due to the recently submitted u-boot-arm/master pull request being NAKed by Tom: the content of this pull req was exactly that of the latest u-boot-samsung/master pull req and was a fast forward from previous u-boot-arm/master (28e5ac2d) which had received extensive testing from Tom.
Therefore, as a roll back of u-boot-arm/master was both easy to perform and safe(r) from a release perspective, I decided to stray from formal master branch management rules and force it back to 28e5ac2d.
Quoted 9 lines
All: if you intend to send a pull request to u-boot-arm/master, please rework this request to take this rollback into account.
Minkyu: for the reasons above, I suggest you roll u-boot-samsung/master back to 28e5ac2d before building and sending an amended pull req, but of course the choice is yours.
OK. I'll revert soft i2c patches and send new pull request at next Monday.

Quoted 6 lines

Quoted 3 lines
sorry. spi, not i2c.
Quoted 1 line
Is it OK?
It's ok, but note that it won't be included in the 2012.10 release
anyway, as monday is the release date.

Indeed. If you want to split out any critical fixes from the spi patches and get that out today or tomorrow I can build-test things again.

- --
Tom

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQIcBAEBAgAGBQJQeCpXAAoJENk4IS6UOR1Wxy4P/0WNN+lMAt9/gutSdOR+ZjnF DqnlcTtNATqsoSzBYToHvineXmvHrz7G00MATgIE8rXvv+cIOnuvJJCmDv8+FAza 0qtaJCA61c7K05A6RyvnXs829kDpHvak10VfeAdDQ/XvBUSo+lePALp+q2KzHgx1 /TfjXrhkvl8WQsjgtmdrFdHSZnnpJoEi0TTXOmqllawmElapEh9ZOcNUazfN7/pj 51SxtXNb/oc4yXC8hJpILk+ArtACVPktU6SPnhnco1j43RQ4Q1REFUonZW1H0SNV gaJqsYrXc4f7z+zgDZjtjCXp7S21P88bHbvw8PoPBuJC+ipxwL4dkSlpwoC//5s1 5ooGEBVJ44PlYagwj7ThcAlOy6zuOahCT7dDYN6/6EWPbf5REfl04kf6ObBgigN7 BmxVko6mFTYLsWXQY6xHvyWf1OG/2vLMUr3zqkco5W4VkKOLn/+wHktLcqnBghAC NqY9eh1oUrWSQq1RHrJWoXHDPLxv0Mcq/EUN0IclY9xM+4KW4TFlxD+kO6hxNpGJ zv1wIfRUM+jkEgCoX75IajBwtMU9Q1QF2NABnsyoxfeBOy+2b3nzsKvwSwXLlthD 9UwKu1TaAC9LHP4cZSg1foMaiukQM2IfaB7+55fQ6R8MK0ZmzN7CHclQI0ok+NhT wCfbiI3vlptpqW1+qc2c
=2jCx
-----END PGP SIGNATURE-----