From: "Iván Briano" <sachi...@gmail.com> To: "Enlightenment developer list" <enlightenment-devel@lists.sourceforge.net> Cc: enlightenment-...@lists.sourceforge.net Sent: Tuesday, July 3, 2012 3:52:45 PM Subject: Re: [E-devel] E SVN: devilhorns trunk/evas
2012/7/3 Carsten Haitzler <ras...@rasterman.com>: > On Tue, 03 Jul 2012 17:45:57 +0300 Tom Hacohen <t...@stosb.com> said: > >> On 03/07/12 17:34, Iván Briano wrote: >> > 2012/7/3 Enlightenment SVN <no-re...@enlightenment.org>: >> >> Log: >> >> Evas: Update ChangeLog wrt Tizen Merge. >> >> >> >> NB: This is the commit message inside tizen git for this commit. Don't >> >> blame me if the message is not detailed enough for you. Complain to >> >> the original committer about making more detailed commit messages. >> >> >> > >> > I say we reject changes unless they specify clearly what they do. >> >> Yeah, we even talked about it on IRC and you agreed... You should not >> commit things you don't know what they do. You can't know if the commit >> is correct, buggy, or implements an unwanted behaviour. > > that's part of a merge or review process. you need to find all the changes, > break them up into features/sets and have info what it does and why and who > did > it and THEN commit that. but get that info together. i've done this before. > it > took me months. > >And we are going through that again? Future changes will be the same or will >the people behind those changes learn to keep enough of a history to make >merging easier? It sounds a lot like they don't give a damn. 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. dh > -- > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > The Rasterman (Carsten Haitzler) ras...@rasterman.com > > > ------------------------------------------------------------------------------ > > 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 ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ 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
