On Tue, 26 Nov 2013 09:16:31 +0900 Carsten Haitzler (The Rasterman) <ras...@rasterman.com> wrote:
> On Mon, 25 Nov 2013 17:05:55 -0200 Gustavo Sverzut Barbieri > <barbi...@gmail.com> said: > > > On Mon, Nov 25, 2013 at 10:01 AM, Cedric BAIL <cedric.b...@free.fr> wrote: > > > On Mon, Nov 25, 2013 at 12:30 PM, Tom Hacohen <tom.haco...@samsung.com> > > > wrote: > > >> > > >> This reminds me. Let's git rid of this changelog and news none-sense > > >> already. > > > > > > Sounds like a good move... when we will have a proven record of usable > > > commit message to generate a ChangeLog and NEWS from it ! > > > > it would be very beautiful to spot bad committers, not only bad messages: > > > > Raster(1234): > > Fix stuff > > no such commit log from me (not in efl, elm or e) > > > dbg-- > > yes - and that tells you want you need to know. removing debugging. everythng > you need is there. i don't see why it needs to be more descriptive. also no > such commit log in e, efl or elm > > > Fix break due remove dbg > > and again - told you what you need to know (and no such commit log as above - > i > searched and found none of these). > > i wrote all my commit logs ASSUMING people digest them via the svn comits > list. > that means they get the log AND the diff below. if the diff is trivial why > should i repeat in the log what the diff already says ? git log -U will do the > same. i always did it this way to save repeating information you already have, > but it seems everyone likes to not use the information they already have. > > > :-D > > > > -- > > Gustavo Sverzut Barbieri > > -------------------------------------- > > Mobile: +55 (19) 9225-2202 > > Contact: http://www.gustavobarbieri.com.br/contact not trying to jump on any bandwagons here (I don't really care about commit messages in e), but it WOULD be great if people could try and review changes to split things a bit more effectively wrt formatting/trivial vs other changes. as an example, and I know this was a one-time thing, the elm theme change commit was HUUUUUUUUUUUUGE because 90% of it was pofile stuff. I was skimming the commit in git log trying to find one line which got changed and it took a while since my terminal pager was screwed up and wouldn't search. similarly, a lot of people use editors which enforce various whitespace formatting styles. this means that just opening a file will generate some changes. if a big commit goes in, these types of unnecessary changes do make the commit more annoying to read through if I'm going back at a later date to figure out whether a regression occurred. again, I'm not calling you or anyone else out specifically on this; I know I'm guilty of it as well. I'm trying to improve my own usage though, and it would be great if the rest of the community would put in a little extra time reviewing their changes before pushing in consideration of people who might later review the commits. ------------------------------------------------------------------------------ Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
