Re: Need advice on when to commit and how many commits to issue when multiple files changed

2010-10-13 Thread Ryan Schmidt
On Oct 13, 2010, at 14:05, LiuYan 刘研 wrote: > > BTW, CVS tagging is very nice, 'tagging' (svn copy) in subversion is like an > extra commit and result in a new revision, although 'svn copy' is a > light/cheap > way in subversion, it still make me confused sometimes. Do not let it confuse you.

RE: Need advice on when to commit and how many commits to issue when multiple files changed

2010-10-13 Thread Bob Archer
> David Weintraub gmail.com> writes: > > > > > On Wed, Oct 13, 2010 at 2:25 AM, LiuYan 刘研 > 21cn.com> wrote: > > > Hi all, > > > Because a single svn commit will result in a whole new revision > tree, so > > > currently I commit all changes once per day after work (to > avoid too many > > > revi

Re: Need advice on when to commit and how many commits to issue when multiple files changed

2010-10-13 Thread David Weintraub
On Wed, Oct 13, 2010 at 3:05 PM, LiuYan 刘研 wrote: > David Weintraub gmail.com> writes: > BTW, CVS tagging is very nice, 'tagging' (svn copy) in subversion is like an > extra commit and result in a new revision, although 'svn copy' is a > light/cheap > way in subversion, it still make me confused

Re: Need advice on when to commit and how many commits to issue when multiple files changed

2010-10-13 Thread LiuYan 刘研
Ryan Schmidt ryandesign.com> writes: > > > On Oct 13, 2010, at 01:25, LiuYan 刘研 wrote: > > > I'm new to subversion. I used CVSNT before. > > Welcome! > > > Because a single svn commit will result in a whole new revision tree, so > > currently I commit all changes once per day after work (to

Re: Need advice on when to commit and how many commits to issue when multiple files changed

2010-10-13 Thread LiuYan 刘研
David Weintraub gmail.com> writes: > > On Wed, Oct 13, 2010 at 2:25 AM, LiuYan 刘研 21cn.com> wrote: > > Hi all, > > Because a single svn commit will result in a whole new revision tree, so > > currently I commit all changes once per day after work (to avoid too many > > revisions because of my o

Re: Need advice on when to commit and how many commits to issue when multiple files changed

2010-10-13 Thread David Weintraub
On Wed, Oct 13, 2010 at 2:25 AM, LiuYan 刘研 wrote: > Hi all, > Because a single svn commit will result in a whole new revision tree, so > currently I commit all changes once per day after work (to avoid too many > revisions because of my old CVS habit). > > But I'm afraid it's not a proper way, so:

RE: Need advice on when to commit and how many commits to issue when multiple files changed

2010-10-13 Thread Loritsch, Berin
> > Hi all, > > I'm new to subversion. I used CVSNT before. > > Because a single svn commit will result in a whole new > revision tree, so currently I commit all changes once per day > after work (to avoid too many revisions because of my old CVS habit). There's no particular reason to do tha

Re: Need advice on when to commit and how many commits to issue when multiple files changed

2010-10-13 Thread Nick Stolwijk
I try to commit the smallest amount of work worth committing. ie. Add 1 unit test, add code to make it all happen, commit. At least, that is the ideal situation, most of the times it will amount to the work done for one jira issue, or anything in between. But all code commited together at least ref

Re: Need advice on when to commit and how many commits to issue when multiple files changed

2010-10-13 Thread Ryan Schmidt
On Oct 13, 2010, at 01:25, LiuYan 刘研 wrote: > I'm new to subversion. I used CVSNT before. Welcome! > Because a single svn commit will result in a whole new revision tree, so > currently I commit all changes once per day after work (to avoid too many > revisions because of my old CVS habit). >

Need advice on when to commit and how many commits to issue when multiple files changed

2010-10-13 Thread LiuYan 刘研
Hi all, I'm new to subversion. I used CVSNT before. Because a single svn commit will result in a whole new revision tree, so currently I commit all changes once per day after work (to avoid too many revisions because of my old CVS habit). But I'm afraid it's not a proper way, so: - Should file