2008/5/13 David Smalley <[EMAIL PROTECTED]>: > > I was curious as to why the whole query_revision process needs to > happen if "HEAD" will suffice as a revision?
2 reasons: 1. people want to deploy what they have (tested) locally, and a local HEAD might differ from remote HEAD. explicit commit ID makes sure that there is no surprise; 2. you can set the ":branch" option in your recipe to anything other than "master" or "HEAD", but the local branch/tag name you are using may not exist remotely (or might be under a different name). explicit commit ID is a painless way to stop worrying about naming local branches same as remote. --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
