Re: commit

In linux you can define what you want to commit with svn commit
<file/folder list>. You can also double check the commit message
editing screen (by not using -m <message>) to see if there are files
you don't want committed, another way is svn diff | grep "Index:"

In windows with tortoisesvn it will show you a list of file which are
going to be committed and you can exclude them

Yes for public members it's mandatory, but I'd go also for private
members in order to help who is going to work on it in future,
including in-code comments for not really self commenting code (or
which would need to track what is going on in several methods)

2012/6/17 Eunsoo Roh <[email protected]>:
> Thanks for the catch. I agree that shouldn't have been committed. Is there
> any way to exclude certain files from committing?
>
> In case of comments, you mean doxygen comments for public
> classes/structs/methods?
>
> Eunsoo
>
>> Date: Sun, 17 Jun 2012 09:01:37 +0200
>> Subject: commit
>> From: [email protected]
>> To: [email protected]; [email protected]
>
>>
>> Hi,
>> some comments regarding the previous commit:
>>
>> +; Disable texture compression.
>> +Video.OpenGL.UseExtension.GL_ARB_texture_compression = false
>>
>> It shouldn't be added to master files in cs.
>>
>> Another thing remember to comment all variables in classes and structs
>> and to comment the arguments of methods.
>> While there, even if the previous code had variables named for example
>> "p" as input arguments maybe it could be a good idea to change them to
>> more explicit names.
>> Last thing be careful with the trailing spaces in a line.

------------------------------------------------------------------------------
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/