Re: large commits or small commits?

On May 22, 2006, at 22:49, Konrad Rosenbaum wrote:

> It is usually recommended to commit each piece of functionality as
> its own
> revision, because it enables you to provide them as single patches to
> outsiders or to revert a single step that turned out to be wrong by
> reverse-merging a single revision.

Another model is to create a branch for one line of work. Then the
person doing that work can commit whenever they want. When the work is
ready, it is merged into the trunk or another branch in a single
commit. The frequent or common commits give the benefit of saving
work, creating a record, et cetera, and the merge gives the benefit of
having a single commit of the whole work.

                                -- edp (Eric Postpischil)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 23 18:32:12 2006