On 03/07/12 18:31, cpmicha...@comcast.net wrote: > Well, that makes all this merging nice and simple then. Ok, merging done !! > :) Since none (or hardly any) of the tizen git commits rarely ever specify > what they do/or fix, then none (or hardly any) of it will get committed > anymore. Makes the process much simplier ;) > > > On a serious note tho, alright no problem. I can spend the time tracking down > the people who did the commits and getting some sort or (hopefully) sane > response from them about what it fixes, etc, etc. Then apply & > test....assuming that goes well, then maybe commit. Just be aware that, like > you said raster, it may take months.
You can alternatively just read the patches and find out what they are supposed to do and write changelog entries, news entries and commit logs accordingly. :) Would probably be easier. -- Tom. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
