[oe] A question of workflow
pmiscml at gmail.com
Sun Jan 7 22:16:32 CET 2007
Sunday, January 7, 2007, 10:04:24 PM, you wrote:
> On So, 2006-12-31 at 10:45 +0100, Koen Kooi wrote:
>> > This is simply because we have no established way of receiving data
>> > through the SCM for merging into trunk without direct write access.
>> > my other email says, I'd like to find a way of supporting that but
>> > probably an education issue on both sides.
>> And the fact that we usually have to tweak 80% if the patches we
> If you do that, can you commit the patch from the original author
> literally on a branch, then apply your own changes which fix it on top
> of the original patch and then merge back into the main trunk? I did an
> experiment and found that this considerably eases the pain for external
> What do you think? Did I miss something?
Well, why would OE core developers (err, what about non-core
developers - we also care for contributed patches - after all, to get
commit access to OE, you first contribute bunch of patches) - well, why
would they do that? OE is open-source project, there's no position of
"patch processor", and people do what they find useful, leaving some
share of their for patch processing. Any complex and artificial rules
won't work. Just in case, there's always another alternative - contributors
just should submit patches in the perfect form, suitable for merging w/o
tweaks. Obviously, it's just the same not attainable, nor it's really
*that* important - we want people contribute more than either us or them
to follow strict rules.
Just my IMHO - I'm not a core developer ;-).
Paul mailto:pmiscml at gmail.com
More information about the Openembedded-devel