I noticed this hasn't made it to master yet. Could it? I'm running
sprints and there's a bit of confusion on how to contribute to git.
Cheers,
Jeremy
On Thu, Jun 7, 2012 at 9:53 AM, Aymeric Augustin
wrote:
> On 6 juin 2012, at 21:09, Anssi Kääriäinen wrote:
>> I am sure there is still a lot
On Fri, Jun 8, 2012 at 7:57 AM, Anssi Kääriäinen
wrote:
> On 8 kesä, 17:28, Luke Plant wrote:
>> First, thanks so much to Aymeric and Anssi and others for the
>> contribution guidelines, they're very helpful.
>>
>> I've got some questions that are due to my ignorance of git (I have
>> managed to
On Sun, Jul 15, 2012 at 11:07 AM, Jeremy Dunck wrote:
>
> That is indeed what I meant, but I think Anssi's probably right that
> this belongs in contribute_to_class instead of a new adhoc thing in
> ModelBase.__new__.
>
> I'll take a swing at making this change.
>
> Opened related ticket: https://
On 18 juil. 2012, at 11:46, Jeremy Dunck wrote:
> I noticed this hasn't made it to master yet. Could it? I'm running
> sprints and there's a bit of confusion on how to contribute to git.
Hi Jeremy,
This was committed. It's under Docs > How to get involved > Working with Git
and GitHub.
https
I'd like to open up a discussion on the possibilities of having a way to
optionally specifying not to create operator indexes on CharField's when
db_index=True. Based on the consensus from this discussion, I'll open up a
ticket and if it is within my abilities, generate a patch.
For background
On Thu, Jul 19, 2012 at 2:19 AM, Eric Floehr wrote:
> I'd like to open up a discussion on the possibilities of having a way to
> optionally specifying not to create operator indexes on CharField's when
> db_index=True. Based on the consensus from this discussion, I'll open up a
> ticket and if it
