@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 -~----------~----~----~----~------~----~------~--~---
