Yep.. svn diff is important before a commit.. and watch out for something.. we have had quite a few times some annoyance where you do your modifs, then you 'svn update', then before you commit, you check your emacs and realize you didn't save, so you save, then you svn commit.. in the meantime, you just saved the file with your modifs as it was before the svn update, so if someone commmitted something in the menatime, his changes disappears after you do a commit.. so watch out for that, make sure you saved all your files, THEN do the svn update, THEN do a svn diff jut to make sure you didn't forget a 'puts' or whatever, then commit.. We're faily nice here, so no real management, no real 'do not commit a fix without it being in the task list first" and blabla, so you can do your changes and commit them as you like, mainly for bugfixes, but when it's anew feature, you should always discuss here first.. sometimes we have a better solution, sometimes we don't want to waste the time on some extra thing, sometimes we don't want to add an extra advanced option in order to keep the prefs window non bloated, etc.. you'll get used to how we work pretty fast I think.. you already noticed how we do things lately. About Boris's ps.. don't trust him, don't listen to him.. @Boris.. are you mad?? why say I'm not a dictator, just when I wanted to start my dictatorship with the new devel, you ruined my reputation, blablabla :p
Thx Boris for taking the time, thx Cristo (can I call you that ?) for the contributions and help! :) One last thing, Cristofaro, can you create (if not already done) a Sourceforge account and give me your username (and password please, lol) so I can add you to the team when the time comes ? Thanks, KaKaRoTo On Fri, Dec 15, 2006 at 01:22:28PM +0100, Boris Faure (aka billiob) wrote: > Hi Cristofaro. > Thanks for joining the team. > > I'm almost sure you know how to update your local svn repository. > Instead of sending patch, this is how you should do (when you'll have > an access to svn) > $ svn update > and check if you doesn't have conflicts > $ svn diff > to check your changes > $ svn commit --message "my first commit :) about ....." > or $svn commit FILES --message "my first commit :) about ....." > > (yep, i should follow those rules :s ) > > there's also svn blame which is interesting, .... > > You may want to suscribe to amsn-commits mailing list : > http://sourceforge.net/mailarchive/forum.php?forum_id=41292 > > and maybe more, but i don't have the time to finish. > > cya, and welcome ! > > Ps: don't worry, Youness Alaoui is not a dictator, and if he gave > tasks to you that you don't feel like coding those, you can leave > them. > -- > Boris FAURE (aka billiob) > mail, msn : [EMAIL PROTECTED] > No trees were killed in the sending of this message. > However, a large number of electrons were terribly agitated. > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Amsn-devel mailing list > Amsn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/amsn-devel ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
