hat common choose to auto-migrate just
part of the application database.
This would also make the path more smooth to people wanting to change
their app to be auto-migratable.
Thanks,
--
Dalton Barreto
http://daltonmatos.com
--
You received this message because you are subscribed to the Go
Em 18 de abril de 2012 21:13, Luke Granger-Brown escreveu:
>
> On Wed, Apr 18, 2012 at 11:55 PM, Dalton Barreto
> wrote:
>>
>> Em 18 de abril de 2012 19:46, Dalton Barreto
>> escreveu:
>> > Em 18 de abril de 2012 18:44, philipn escreveu:
>>
>> Hm
Em 18 de abril de 2012 19:46, Dalton Barreto escreveu:
> Em 18 de abril de 2012 18:44, philipn escreveu:
>> Hey folks!
>>
>> I started a wiki page to help plan a migration to GitHub:
>>
>> https://code.djangoproject.com/wiki/GitHub%20Migration
>>
>&g
; (attaching patches, etc) is less accessible to non-core contributors than
> GitHub and I'd love to do anything I can to help make this better.
>
Maybe the best way to avoid that people create issues on github is to
disable it for the
official repository. This is possible through the G
ecome nontrivial.
Maybe using the first approach with an message next to the checkbox
saying: "Uncheck if you don't want to receive an email about this
update"
or something similar would be enough.
--
Dalton Barreto
http://daltonmatos.com
--
You received this message because
could work, but if the plugin checks the box on every request a
user that do not want to receive the updates must uncheck every time
he updates a ticket.
Would it be a good idea to use a cookie, so the plugin would
"remember" what the user wants? or would it be too much?
What do you thi
