Guys, sorry for long silence. I had no time to study chainsaw, I had to chop wood :)
On 23 нояб, 02:52, Lukas Kahwe Smith <[EMAIL PROTECTED]> wrote: > i prefer small teams and there i prefer a commit often approach for > things that people work on together to keep people in the loop. when > people work on something on their own, then its not so ueber critical > that there is a migration anyways, so in that case i am also not so > concerned. Unfortunately this approach means that you won't keep zero-knowledge revisions: any other developer will have to know that this revision is actually not for checking out. This works ok for branches, but not for trunk I think. > > > 3) it should be handy and maximally automatic. What you're saying > > about - to make backup files - seems messy to me. Unfortunately I must > > admit I would use `schema-diff schema.yml .svn/text-base/ > > schema.yml.svn-base` instead of your way. As I would say, it's the > > least of evils :) Probably some script would do backing up, but again, > > it should follow the requirement #1, so as I see something like svn > > keyword $id: $ will be a must some way. > > well if it makes you happier you could use svn:externals to point to > the earlier revision of the file (not sure if that is actually legit > in svn). It's not a way either. At least because you can't create an external pointing to a single file. And this is not less maintenance nightmare than just backing up. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
