You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Kamaraju Kusumanchi <ra...@gmail.com> on 2006/05/23 04:55:25 UTC
large commits or small commits?
Hi
I am sort of newbie to version control systems. I searched the archives at
http://subversion.tigris.org/servlets/SearchList?listName=os400 but could not
find anything related to this issue.
1) As a rule of thumb, would you advice commits involving large amounts of
changes or small chunks of changes (but done multiple times)?
2) I tend to do commits involving small chunks of changes each time. Each
commit will give me one additional functionality or fixes a bug in the code
etc., But due to this, my repository version number is in hundreds which I
think is very large. Are large repository version numbers bad in any way? Is
it something to be worried about?
thanks
raju
--
http://kamaraju.googlepages.com/cornell-bazaar
http://groups.google.com/group/cornell-bazaar/about
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: large commits or small commits?
Posted by Eric Postpischil <ed...@apple.com>.
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
Re: large commits or small commits?
Posted by Konrad Rosenbaum <ko...@silmor.de>.
On Tuesday 23 May 2006 06:55, Kamaraju Kusumanchi wrote:
> 2) I tend to do commits involving small chunks of changes each time. Each
> commit will give me one additional functionality or fixes a bug in the
> code etc., But due to this, my repository version number is in hundreds
> which I think is very large. Are large repository version numbers bad in
> any way? Is it something to be worried about?
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.
Big revision numbers are nothing to be afraid of, eg. KDE is now (7:45
Berlin time) at rev 543910 - this usually increases a few times per hour...
Konrad
Re: large commits or small commits?
Posted by Kamaraju Kusumanchi <ra...@gmail.com>.
On Tuesday 23 May 2006 01:58, Steve Williams wrote:
> Kamaraju Kusumanchi wrote:
> >2) I tend to do commits involving small chunks of changes each time. Each
> >commit will give me one additional functionality or fixes a bug in the
> > code etc., But due to this, my repository version number is in hundreds
> > which I think is very large. Are large repository version numbers bad in
> > any way? Is it something to be worried about?
>
> Absolutely nothing to be worried about. You would need to do several
> thousand commits every hour for many years before you would even have to
> think about it being a problem.
Thanks for all the replies. This and the KDE example by Konrad clarifies
things a lot.
raju
--
http://kamaraju.googlepages.com/cornell-bazaar
http://groups.google.com/group/cornell-bazaar/about
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: large commits or small commits?
Posted by Steve Williams <st...@kromestudios.com>.
Kamaraju Kusumanchi wrote:
>Hi
> I am sort of newbie to version control systems. I searched the archives at
>http://subversion.tigris.org/servlets/SearchList?listName=os400 but could not
>find anything related to this issue.
>
>1) As a rule of thumb, would you advice commits involving large amounts of
>changes or small chunks of changes (but done multiple times)?
>
>
>
We generally keep one changeset per commit. That way, we can easily
merge changes between branches.
>2) I tend to do commits involving small chunks of changes each time. Each
>commit will give me one additional functionality or fixes a bug in the code
>etc., But due to this, my repository version number is in hundreds which I
>think is very large. Are large repository version numbers bad in any way? Is
>it something to be worried about?
>
>
Absolutely nothing to be worried about. You would need to do several
thousand commits every hour for many years before you would even have to
think about it being a problem.
--
Sly
This message and its attachments may contain legally privileged or confidential information. This message is intended for the use of the individual or entity to which it is addressed. If you are not the addressee indicated in this message, or the employee or agent responsible for delivering the message to the intended recipient, you may not copy or deliver this message or its attachments to anyone. Rather, you should permanently delete this message and its attachments and kindly notify the sender by reply e-mail. Any content of this message and its attachments, which does not relate to the official business of the sending company must be taken not to have been sent or endorsed by the sending company or any of its related entities. No warranty is made that the e-mail or attachment(s) are free from computer virus or other defect.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org