On Wed, Apr 28, 2010 at 12:02:57PM +0200, Carsten Munk wrote: > Hi, > > I noticed the following lines in > http://meego.gitorious.org/meego-os-base/kernel-source/blobs/master/README#line120 > : > > * Unless the author identified in the From: tag has a @intel.com or > @linux.intel.com address, the patch must include a Signed-off-by: or > Acked-by: header which identifies the person in one of these domains > who feels responsible for the patch inside the company. > > Would it be possible to reword this in a manner so it does not sounds > as biased towards Intel employees? Ie, treating non-member > contributions with same process and review as member contributions. > > A suggestion could be referring to upstream approval by subsystem > maintainer or by someone responsible for the subsystem/architecture in > the MeeGo kernel maintainer team.
Heh, that file is copied directly from the suse kernel tree, with only s/suse/intel/ applied to it there. The reason that we (Novell) require this, is that we want someone to "own" the kernel patch so that we know who to blame if something goes wrong. As Intel is ultimately responsible for distributing and maintaining this kernel tree, having someone within intel to "own" each patch in the same manner makes lots of sense as well. So I would recommend just leaving it alone, unless you want to maintain the whole kernel package for intel yourself? :) thanks, greg k-h _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
