On Mon, 2013-03-04 at 11:33 +0100, Martin Jansa wrote: > On Mon, Mar 04, 2013 at 10:11:27AM +0000, Richard Purdie wrote: > > On Mon, 2013-03-04 at 09:18 +0100, Martin Jansa wrote: > > > On Sun, Mar 03, 2013 at 08:34:30PM -0500, randy.macl...@windriver.com > > > wrote: > > > > From: Jackie Huang <jackie.hu...@windriver.com> > > > > > > > > The hardcoded paths in libtool will cause apache2 compile fail at > > > > link stage when the package apr is installed from sstate cache, so > > > > add libtool to SSTATE_SCAN_FILES. > > > > > > > > [ CQID: WIND00405372 ] > > > > > > You can drop this. > > > > Is this really a big problem? I can understand people wanting to be able > > to track commits back to defect reports... > > Not big problem, but isn't link to cgit in their tracking system enough? > > That's what I'm using for SHR bugs now, because I cannot assume that people > using oe-core will know where bug tracker for [SHR #666] is.
I am quite happy for the meaning of some of these to be documented somewhere with a link to the appropriate bugzillas or other systems. > I cannot find public windriver bug tracker where I can search > WIND00405372 to find longer description why this change is needed (I > know why in this case) - that's why I find yocto bug tags useful, but > not WIND00*. As per the commit guidelines, these are additional information and no excuse for not writing a self-standing commit message. Some will be more useful than others but I'm not sure it makes sense to remove them just for the sake of it. Cheers, Richard _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
