Re: Switching SCM to git and commit/review policy

[Rolf Leggewie <no2spam@nospam.arcornews.de>]

Otavio,

thank you for clarifying.

Otavio Salvador wrote:
> The revisions will be a moving target. To tag a commit as "not-ok"
> you'd need to amend it and  them change it rev number.

I was talking about a possible workflow with absolute disregard as to
how it is supported by tools out there, git in particular.  I think, at
this point in time it is OK to build your castle in the sky and worry
about how to implement that with tools later (and possibly make
necessary adjustments, then)

>> Modules?  Are you talking kernel?  Or are you using modules as a synonym
>> for recipe?
> 
> recipe, sorry.

Well, that is certainly nice, but not sufficient.  bitbake will not
necessarily rebuild an app if a lib changes IIRC.

> human. I think that a sort of compile tests are enough to kill most of
> problems.

NACK.  I don't agree.  They are necessary and good to be done.  They are
still insufficient.  Otherwise, we could fully automate the review
process and have a compile firm to automatically reject changesets that
lead to compile failures.

Regards

Rolf