Difference between Shelve changes and create patch?

This may sound like a very obvious and dumb question but...

Can someone explain the differences between these two VCS actions as the look to me like they do pretty much the same thing.

The only thing that I can think of is that a patch is stored away and kept when you close the project where as a shelf is local and lost if you close the project.

3 comments
Comment actions Permalink

Hello dave,

This may sound like a very obvious and dumb question but...

Can someone explain the differences between these two VCS actions as
the look to me like they do pretty much the same thing.

The only thing that I can think of is that a patch is stored away and
kept when you close the project where as a shelf is local and lost if
you close the project.


Shelve Changes rolls back the changes you've made when you shelve them, and
automatically keeps track of the changes you've shelved. Also, shelved changes
definitely aren't lost when you close the project.

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Well, you can mail patches to someone whose working on the same project, which you really can't do with shelved changes. Also, patches are great for moving changes between different branches of the same project, which shelved changes really can't do. OTOH, with shelved changes you don't have a file that you have to worry about accidentally deleting/losing/forgetting.

In practice, I use patches for communicating with other developers, and shelved changes for handling my own internal workflows. From an implementation point-of-view, they seem to be just two different ways of presenting the same (cool and very handy) technology.

--Dave Griffith

0
Comment actions Permalink

Thats great,

Thanks guys

0

Please sign in to leave a comment.