• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Understanding Subversion commits and revisions

 
Hussein Baghdadi
clojure forum advocate
Bartender
Posts: 3479
Clojure Mac Objective C
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hey,
I'm trying to dive more into Subversion.
http://svnbook.red-bean.com/en/1.5/svn.branchmerge.using.html
At this point, you should understand how each commit creates an entirely new filesystem tree (called a “revision”) in the repository.

Does this mean if a some one changes index.jsp page (in a Java web application for example), SVN will copy the entire project folder and increase the revision number?
Is this operation happens for every change?
I don't know but I got the feeling it is expensive approach.
Thanks.
 
David Newton
Author
Rancher
Posts: 12617
IntelliJ IDE Ruby
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It'd be really easy to see the increase in file space usage after making a change, no?

Svn stores diffs.
 
Hussein Baghdadi
clojure forum advocate
Bartender
Posts: 3479
Clojure Mac Objective C
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What do you mean by "diffs"?
The modified file (index.jsp for example)?
 
David Newton
Author
Rancher
Posts: 12617
IntelliJ IDE Ruby
 
Peter Johnson
author
Bartender
Posts: 5852
7
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The text you quoted is in regard to branching and merging. Changing a single JSP file does not involve either a branch or a merge, thus there is no new directory tree. When checking in a text file the only thing that will be added to the repository is the difference between the current version and the previous version of the file. And the revision number does change for the whole repository.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic