On Sun, 30 Jan 2011 08:43:22 +0100 (CET) Vincent Torri <vto...@univ-evry.fr> said:
> > > On Sun, 30 Jan 2011, Carsten Haitzler (The Rasterman) wrote: > > > On Sat, 29 Jan 2011 16:31:31 +0100 (CET) Vincent Torri <vto...@univ-evry.fr> > > said: > > > >> > >> > >> On Sat, 29 Jan 2011, Carsten Haitzler (The Rasterman) wrote: > >> > >>> On Sat, 29 Jan 2011 14:30:24 +0100 (CET) Vincent Torri > >>> <vto...@univ-evry.fr> said: > >>> > >>> never used it. never have used it. any new tool WILL result in there being > >>> errors. so you're a bit optimistic. > >> > >> It's not a new tool (you didn't even check when it has been written > >> otherwise you would not say that). > > > > it's a new tool - i had to apt-get install it. hell - it isnt even obvious > > as to HOW to use it. > > > > moap changelog ... now what? diiff? > > did you ever read my mails ????? I sent several mails about that. I > already said HOW to use it ! no - because i have an inbox with 20,000 mails just for e-devel. you think i'm going to search through it when i can fix the problem with just quickly editing the text file? the problem is solved. done. i spend more effort replying to you than it takes to edit the cahngelog AND fix the problem > > what has a diff got to do with a changelog? > > checkin? checkin files LISTED in the changelog wtf? it wants to force us to > > LISt SPECIFIC FILES changed? hell no. changelog != svn log. > > SO AGAIN, if you are too lazy to read the README file, and if you have > ever read correctly my mails, you would have seen the link of that README: again - so much more work. when a tool takes more work to hunt down docs and use and figure out than to do it the manual way... then that tool loses its usefulness. what you propose is that we REPLACE using svn with moap for doing commits - thats the ONLY way it works. and the ONLY reason is the changelog file. i find that a very weak argument for replacing a tool that has been used and worked for YEARS. sure - it wraps it - but it complicates development anc changes workflow for the sake of 1 single file. you get very upset over that 1 file. you need to calm down. you suddenly expect everyone to go change the way they have done things for many years overnight to a tool YOU love you use. all for the sake of a changelog. moap doesnt magically figure out who submitted the patch. it doesnt magically fix everything. it doesnt magically ensure changelogs are maintained as people can not use it. you need to calm down. iyts JUST a changelog file. its paperwork. its bureaucracy. it doesn't materially affect the object. people aren't adding bugs or making this slow, or leak... its a paperwork file. you are getting upset over paperwork. you need to calm down ad accept the fact that paperwork and tools to fill in paperwork are not worth getting upset over. > when you want to commit, go to toplevel: > > 1) moap cl prep > > 2) edit the ChangeLog, that is: > > a) add the name of the author of the patch, or remove the 2 lines about > the reviewer and author > b) remove the files that you don't want to commit (OF COURSE it will not > force you to commit files you don't want) > c) describe the commits for each file or a group of files. > > 3) moap cl ci -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
