I've worked with Eclipse and TortoiseSVN, and work daily with Versions and SmartSVN. The workflow Quinn lays out is the same I have with SmartSVN and it's so much simpler to do than the cmd+click option, which is really impossible if you have a both wide and deep folder hierarchy. If you do something wrong when trying to just select the correct files, your selection is suddenly gone, you've selected the wrong file(s) or something else.
I'm not trying to plug SmartSVN here, but it's a more mature SVN client than Versions, so it's only natural that it has more features built in. One other such feature in the commit dialog I really love with SmartSVN that works excellently with the workflow in question is to preview the changes made to each and every file inside the commit window, which makes it extremely easy to spot which files you should remove the checkbox on and not. So basically, cmd+click works in theory, but is utterly useless (at least for me) in practice. :) -Asbjørn On Thu, 19 Nov 2009 16:57:12 +0100, Hardy Macia <[email protected]> wrote: > > I've only done the selective commits by selecting files that I want to > commit, not the other way around as you are suggesting, but isn't what > you want to do just... > > Show changed files, select all, cmd-click the file/files you don't want > to commit? > > I've only used Eclipse once for a small project, but I found it > extremely annoying to use. > > -Hardy > > On Nov 19, 2009, at 10:50 AM, Quinn Taylor wrote: > >> It's a matter of workflow preference. Yes, you can select files and >> folders in the main GUI before committing — command-clicking etc. >> obviously works, but just because something is possible doesn't mean >> that's the only way anyone would/should ever want to do it. (Exhibit A: >> Windows) However, it can be a pain for deeply-nested hierarchies and >> excluding that one file that shouldn't be committed yet. The SVN >> plugins for Eclipse provide checkboxes in the commit window, and they >> can be incredibly handy when you need them. However, I generally only >> use them for *removing* files from the commit, so perhaps an >> unobtrusive button in the bottom left corner (which allows you to >> exclude 1 or more selected entries from the commit, without changing >> the selection in the main window) would be a good compromise? >> >> - Quinn >> >> On Nov 19, 2009, at 7:38 AM, Hardy Macia wrote: >> >>> >>> I'm always submitting a few files from versions so that I can submit >>> related file changes together. >>> >>> Cmd-click/shft-click on the files to select the ones you want to >>> submit and submit them. I think checkboxes would get in the way. >>> >>> - Hardy >>> >>> On Nov 19, 2009, at 10:35 AM, [email protected] wrote: >>> >>>> >>>> @Tomo >>>> >>>> "I personally often work on more than one thing on a project, and >>>> when >>>> I want to commit, I would like to be able to commit different things >>>> seperately. " >>>> >>>> Could you not just selected individual files to commit in the list >>>> view or am I missing something? >>>> >>>> "Versions should also know that I have new files and offer me to add >>>> them automatically before commiting" >>>> >>>> Totally agree with this tho :) >>>> >>>> >>>> >>>> On Nov 17, 2:11 pm, Ryan <[email protected]> wrote: >>>>> I have to agree with Asbjørn on both counts. >>>>> >>>>> On Nov 16, 2:43 pm, Asbjørn Ulsberg <[email protected]> wrote: >>>>> >>>>> >>>>> >>>>>> On Mon, 16 Nov 2009 16:35:54 +0100, Ray <[email protected]> >>>>>> wrote: >>>>>>> I agree with the commit UI changes, but this is a workflow issue. >>>>> >>>>>> For some use cases, I agree this is a workflow issue, but for >>>>>> others it >>>>>> isn't. You might want to partially commit your entire working >>>>>> directory >>>>>> because you've been working on several different tasks at once and >>>>>> only >>>>>> want files related to task X commited, but not those related to >>>>>> task Y. >>>>> >>>>>> In such use cases, a checkbox beside each modified file would be >>>>>> neat. >>>>> >>>>>>> I keep a skeleton default config file versioned, and the actual >>>>>>> config >>>>>>> file ignored. Then you never have to worry about committing this >>>>>>> file. >>>>> >>>>>> I do the same thing. Works like a charm. That is, until you change >>>>>> the >>>>>> skeleton file and forget to update the unversioned config file. ;) >>>>> >>>>>> -- >>>>>> Asbjørn Ulsberg -=|=- [email protected] >>>>>> «He's a loathsome offensive brute, yet I can't look away» --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/versions?hl=en -~----------~----~----~----~------~----~------~--~---
