Updating to just a particular revision may work, but it is very easy for the trunk to get into a state where it would be hard to pick out just the fixes by updating specific files to specific revisions. This is labor intensive and confusing, and therefore error prone.
Other people in this thread have suggested branches for the fixes, rather than branches for the features, and I agree with them. It works very well to use branches this way, since the minority of trunk checkins will have to be merged onto the fixes branch, most of your development is simple a checkin-to-the-trunk model. Only when you have a fix that needs to leapfrog ahead of the feature work do you need to merge anything. --Ned. http://nedbatchelder.com Kenneth Gonsalves wrote: > On 18-Jan-08, at 9:54 PM, William Siegrist wrote: > > >> If the spelling changes are in 1 file, and the new feature is in >> another file, can't you "svn update" just the spelling change file >> and not the new feature file? And if they are in the same file, I >> think the --revision option to svn update might also help. >> > > I am an idiot - why didnt I think of that? > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
