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, tom.dev...@googlemail.com 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 <ryan.mcilm...@gmail.com> wrote: >>>> I have to agree with Asbjørn on both counts. >>>> >>>> On Nov 16, 2:43 pm, Asbjørn Ulsberg <asbjo...@gmail.com> wrote: >>>> >>>> >>>> >>>>> On Mon, 16 Nov 2009 16:35:54 +0100, Ray <raimondi...@gmail.com> 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 -=|=- asbj...@ulsberg.no >>>>> «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 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 -~----------~----~----~----~------~----~------~--~---
