[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Nick Stolwijk <nick.stolwijk_at_gmail.com>
Date: Wed, 13 Oct 2010 13:57:05 +0200

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 refers to one jira issue.

Hth,

Nick Stolwijk
~Java Developer~

IPROFS BV.
Claus Sluterweg 125
2012 WS Haarlem
http://www.iprofs.nl

On Wed, Oct 13, 2010 at 8:25 AM, LiuYan 刘研 <lovetide_at_21cn.com> wrote:
> 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 A and B be commited separately?
> - Should file A be commited more than once per day?
> - How to issue these commits when there's 1 single subversion user?
> - How to issue these commits in team working project?
>
> Any advice will be appreciated.
>
>
>
Received on 2010-10-13 13:57:44 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.