I've never used Perforce. It might help to describe the functionality you're looking for.
Versions has a toggle switch in the upper right corner to choose between displaying all files in the working copy, and only files with uncommitted changes. The latter view also includes files which have not yet been added to source control, or hidden via an svn:ignore directive. To elaborate on David's answer, if you haven't selected any files in the working copy when you press Commit, Versions assumes you want to commit all changed files. If some of your changed files are selected, then only those files will be included in the commit, and the rest can be dealt with separately. Thanks, -nat -- Nathaniel Irons Quality Assurer nathan...@blackpixel.com On Nov 20, 2011, at 4:55 PM, Matt Foster wrote: > Thanks, David. I'm used to using Perforce at work, and have found this > functionality in Tortoise as well, so I was hoping there was a similar > solution. > > On Nov 20, 7:17 pm, David Dunham <alakor...@gmail.com> wrote: >>> Is there a way to create a Changelist in Versions so you don't have to >>> submit all working files at once? >> >> Subversion isn't Perforce, but you can certainly select any files you want >> to commit. >> >> David Dunham http://a-sharp.com Twitter: @ASharpLLC > > -- > You received this message because you are subscribed to the Google Groups > "Versions" group. > To post to this group, send email to versions@googlegroups.com. > To unsubscribe from this group, send email to > versions+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/versions?hl=en. >
smime.p7s
Description: S/MIME cryptographic signature
