Re: [PATCH 1/2] linux/kernel: 2.6.32.17, 2.6.33.7, 2.6.34.2 and 2.6.35 are out !

["Yann E. MORIN" <yann dot morin dot 1998 at anciens dot enib dot fr>]

Arnaud, All,

On Monday 02 August 2010 21:37:55 Arnaud Lacombe wrote:
> On Mon, Aug 2, 2010 at 3:30 PM, Yann E. MORIN
> <yann.morin.1998@anciens.enib.fr> wrote:
> > And for even a patch that I thought was trivial, you did spot some
> > issues! :-) So the list is the place to post.
> this unfortunately only apply to externally contributed patches. None
> of the changes you're making can be reviewed before they reach the
> tree, which make crosstool-ng development relatively obscure.

Well, well, well...

Indeed, that's the way it has worked so far. I don't know how I should
proceed... The tree is available for anyone to grab, and I'm willing to
revert any changeset I've made, should I get a report that it breaks on
someone's machine or use-case, in which we'll devise a plan to properly
fix it.

I usualy have no plan for the next release. Mostly the evolution is
Darwinian, in that I have new ideas, and/or needs, and/or peole come
with their needs and/or patches, and if that fits the overall picture,
it goes in the tree. Maybe sometime some refactoring is needed, a fix
is incorrect, or causes other failure, but that usually gets attention
and gets fixed. The big picture is building toolchains. Mostly anything
in that direction is welcome.

One issue I've faced is that every time I've left some patches hanging
on the list without pushing is that no one commented, and the patches
were stale and had bit-rotted (eg. they did not apply properly, and I
was not able/knowledgeable to fix it so it behaved like the submitter
intended).

By no mean did I want to make the process obscur. If you felt I was
trying to, please get this idea out of your head, it was not my
intention, and I'm truly open to suggestions.

Would you find acceptable that I behave like any other contributor, and
push my stuff to the list, wait a few days before I finally push upstream
if there are no comments?

I think I could do that. It will take me some effort to educate myself
not to push directly, and I'm afraid it might slow down the process, but
I can try for the next release...

The real cause for all that is that there is no plan. I don't know where
crosstool-NG is going, besides the fact that its role is to build
toolchains.

Anyway, the current release cycle should be quiet from my side, as I have
another hot topic to hack on. It's using CT-NG as a backend for toolchain
generation for buildroot.

If you have a bright idea, then I'm all hears^Weyes to read it! :-)
[*]

Regards,
Yann E. MORIN.

PS.
[*] Or I just sit on my chair, wait for a patch to come to the list,
tore it down into flames, wait for the second try, criticise it, get
fed up, come up with my own implementation hacked between two coffee,
that turns out to be much more elegant and simple than the previous
attempts, and works... Wait, wait... Last I check on my ID card, my
name was not Linus Torvalds. Sigh... That was a good plan, no? ;-)
YEM.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'



--
For unsubscribe information see http://sourceware.org/lists.html#faq