On 6/8/07, Ben Ford <[EMAIL PROTECTED]> wrote: > Hi Russ, > Thanks for the reply. What's the prescribed way to track multiple patches in > one working copy? I haven't had much experience with patches, but I built my > django base code using patches from a couple of different branch into one > working copy and it caused me problems in that i couldn't then "svn revert" > any of those changes individually...
There isn't anything prescribed; feel free to use whatever works for you. There are any number of patch management tools out there that could make your life easier. > I have no interest whatsoever in forking django or in any kind of conflict, > I suggest this merely as a possibility for consideration. I think it might > be a fairly elegant way to solve some problems, and would be interested in > getting some feedback... If you feel enthused enough to set up a SVK repository, feel free, but the first task that is required is updating the branch to follow the latest changes in trunk. This isn't really a task that can be effectively shared amongst many developers so I'm not sure that an SVK repository will help. However, providing a series of patches that bring the a stale branch up to date (and multi-db is _quite_stale) is one very convincing way to demonstrate that you are serious and capable. Combine that with one or two non-trivial additional bugfixes, and you will have met the criteria for getting SVN access. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
