On 10/5/2012 9:27 AM, Daniel Juyung Seo wrote: > On Sat, Oct 6, 2012 at 1:18 AM, Arjan van de Ven <ar...@linux.intel.com> > wrote: >> On 10/5/2012 9:11 AM, Daniel Juyung Seo wrote: >>> As far as I know, Kibum Kim is away and he is just a SCM guy. >> >> SCM guy ? > > Yes. http://en.wikipedia.org/wiki/Source_Control_Management
I know what SCM is thank you very much What I don't grok is why an "SCM guy" does things and not the package maintainer > He just dumped Tizen source code from Samsung internal git to public Tizen > git. he made a change to Tizen. without any useful commit message, and he replaced one component with another. surely there is a reason and rational for all of that? oh and he didn't dump from an internal git... there would actually be history and other committers if he did that. >> >>> At that time, Tizen didn't keep the internal git histories which is a bad >>> idea. >> >> at that time? This is in August! >> And yes, Tizen HAD a git already at that time.... this was not the first >> commit at all. >> > > Explained above. no actually, not explained at all. there is never an excuse to clobber a git tree. and frankly, this sort of change must be deliberate somehow! or are you telling me that components randomly change like this, without any thought or idea or control? That would be insane, and indicative of a Mickey Mouse project, not something serious. >> which have a last change entry of 2010. >> This change was done in August 2012. >> So these are not very useful files. >> (adding debian files in the commit made sense as part of the general RPM -> >> Debian transition that seems to be happening though) > > No Tizen is moving from deb to rpm and SBS to OBS. > Tizen 1.0 : deb + SBS > Tizen 2.0 : rpm + OBS I feel sorry for you then... sounds like a huge leap backwards. (as someone who has been working on Linux operating systems for 10 years... I can really say I feel sorry for you, with experience, not just compassion) the good news is that in the last few months, debian stuff has been added to, not removed from basically all packages, so I wonder if your statement is actually true. >> >> In what architecture forum was the decision made to switch from the modern >> (C) bootchart to the old (java) bootchart? >> Were there Intel folks, or any non-Samsung folks present in that forum? >> What were the reasons for changing away from the modern bootchart? >> Is Tizen going include Java to work with this? these questions are still very very relevant, and still unanswered. _______________________________________________ General mailing list General@lists.tizen.org https://lists.tizen.org/listinfo/general
