Ben Collins-Sussman <sussman <at> collab.net> writes:
>
>
> On Aug 2, 2005, at 5:13 PM, John wrote:
> >
> > So bottom line, do you think the 'shelveset' idea is marketing-
> > b***? Nothing
> > that can't be achived just as well with branching & merging?
>
> It's not marketing-bull, it sounds like a very nice feature. All
> we're doing is pointing out that the same feature can be accomplished
> by "committing to a temporary branch" and "merging from a temporary
> branch" for *any* version control system. It sounds like MS has
> simply optimized this technique into a single command.
Hi Ben,
In VSTS a shelveset is fundamentally different from a branch - shelving isn't
just UI candy. They're all about keeping updates out of the versioned repository
until ready, while still being able to share them around. When a shelveset is
deleted it's gone forever.
OK, so if this was going to be implemented using the repository, you'd have to
tell it somewhere what path to use for shelvesets ('/branches' or '/shelves').
Shelving would do:
Ask user for a shelve name, and log entry
Create a branch at /shelves/shelvename
Switch to it
Commit changes.
If 'revert' was requested:
Switch back to original location.
If it was being implemented outside the repository, I guess you'd:
Create a patch file.
Prompt user for shelvename and comments
Send the patch, name, comments, userid, base path and revision (yeah it's in the
patch, but probably useful to have it here too).
Send the data out (via SOAP?) to your patch-file storage mechanism.
Revert (optional).
John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 3 09:41:17 2005