On Mon, Nov 16, 2009 at 10:30 AM, Tomo <[email protected]> wrote:
> > Another ridicilously silly thing is, if I change something like the > database config file (wich is only different on my local version), or > application config file, I want to commit stuff without this going up > with them. Right now, I have to revert the changes to these files and > then change them back again to proceed with my work. This is horrible. > > I agree with the commit UI changes, but this is a workflow issue. If you don't ever want changes to this file to be committed, it shouldn't be in version control. For config files, following advice received on this list, I keep a skeleton default config file versioned, and the actual config file ignored. Then you never have to worry about committing this file. -Ray --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
