>From the github:
"* Commits should be atomic: they should each encompass a single logical change that works on its own. You can use "git rebase --interactive" to collapse multiple commits into a single commit before pushing your code up for contribution." I think the idea is to basically have feature branches that are pushed back into Tom's repo as atomic commits... That Should make things relatively easy to deal with right? On Wed, Apr 21, 2010 at 2:33 PM, Jeremy Dunck <jdu...@gmail.com> wrote: On Wed, Apr 21, 2010 at 1:14 PM, Tom X. Tobin <tomxto...@tomxtobin.com> > wrote: > ... > > There are no formal plans (on experimental's side) to merge anything > > from experimental to trunk. Anyone is welcome to package up code from > > experimental and champion a change for inclusion in Django proper, but > > it won't be me; I'm done working with patch files and Trac tickets. > > :-) > > This will be pretty difficult to pull off unless there are feature > branches in -experimental. Will you recommend that, at least? > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-develop...@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com<django-developers%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
