On Thu, Sep 4, 2014 at 7:00 PM, Enrico Scholz <[email protected]> wrote: > "Peter A. Bigot" <[email protected]> writes: > >>>> .inc files make sense with current packaging because they are revision >>>> control friendly. E.g. you can put the logic into .inc and follow its >>>> history with 'git log' which is not possible when there are only the >>>> versioned .bb files. >>> You can follow changes to the .inc but not anything that went in and >>> out of the .bb, but I do concede that git not tracking the renames >>> directly does mean some histories are harder to track (although simple >>> to follow as the commit where the history stops will tell you where to >>> pick it up again). >> >> git log --follow foo_1.2.bb handles 90% of this: > > it's not only 'git log'; it is 'git blame' too and because git does not > support renaming of files natively, the 'git log --follow' method is > error prone and might compare the wrong files resp. fail completely when > there are too much changes. > Did you ever use 'git blame' for few lines most recipes have?
Andreas -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
