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
48Using Patch Files

Occasionally you might want to save a copy of your working copy changes without committing them to the repository. You might decide your changes aren’t yet ready for prime time and that you want to keep them for later (although in this case, creating a feature branch and checking in to the branch is safer). Alternatively, you might be working on an open source project on the Internet and not have commit access to the repository. Instead of committing your changes directly, you need to send them to someone else on the project who has commit access.

Patch files are the Unix world’s solution to this problem. A patch file is a description of changes you have made to some files. You can send the patch file to someone else who ...

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