Skip to Main Content
Pragmatic Guide to Subversion
book

Pragmatic Guide to Subversion

by Mike Mason
November 2010
Intermediate to advanced content levelIntermediate to advanced
150 pages
2h 55m
English
Pragmatic Bookshelf
Content preview from Pragmatic Guide to Subversion
11Committing Changes

Once you are happy with the changes you have made, you should commit them back into the repository. Changes committed into the repository are available to everyone else on your project and are stored securely on your Subversion server. Committing changes is sometimes also known as checking in to the repository; these two terms mean the same thing and can be used interchangeably.

Any time you commit a change into the repository, Subversion will ask for a commit message. Your changes, along with the commit message, then become a revision within the Subversion repository. You should always try to make your commit messages meaningful—they can be used later by someone else (or more often yourself!) to figure out the intent ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Start your free trial

You might also like

Reinventing the Organization for GenAI and LLMs

Reinventing the Organization for GenAI and LLMs

Ethan Mollick

Publisher Resources

ISBN: 9781680500035Errata Page