On Wednesday 03 October 2012 13:43:30 Koen Kooi wrote: > Op 3 okt. 2012, om 13:29 heeft Paul Eggleton <[email protected]> het volgende geschreven: > > On Wednesday 03 October 2012 13:27:41 Koen Kooi wrote: > >> Op 3 okt. 2012 om 12:43 heeft Paul Eggleton > >> <[email protected]> > > > > het volgende geschreven: > >>> On Wednesday 03 October 2012 12:24:19 Koen Kooi wrote: > >>>> Squash those "import" with the "fix" commits, no sense in having a > >>>> broken > >>>> recipe in there. > >>> > >>> I'd rather not - there is sense in being clear about the changes, > >>> because > >>> there are a large number of them in this case. > >> > >> The broken recipes are still available in OE classic if people want to > >> compare them. I still don't get why you want to have broken recipes in > >> the > >> tree at multiple points in your series. > > > > Because I want to easily see in "git blame" where particular lines came > > from - did I add them, or have they been around for ages? > > Does oe-core have the same flow for new recipes?
You already know the answer to this. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
