On 10/20/06, Ramdas S <[EMAIL PROTECTED]> wrote:
> How do I integrate the per-object-permissions trunk to my regular django
> trunk which powers the web site.
>
> I checked the per-object-permissions trunk it works properly at least as far
> as my simple cms apps are concerned.
>
You'll have to d
How do I integrate the per-object-permissions trunk to my regular django trunk which powers the web site.I checked the per-object-permissions trunk it works properly at least as far as my simple cms apps are concerned.
Ramdas On 10/20/06, Jay Parlar <[EMAIL PROTECTED]> wrote:
Since I saw my name (i
Since I saw my name (incorrectly spelled) show up in this thread, I'll
throw my 2 cents in (That's CDN, now almost worth 2 cents US!)
I'm using Chris Long's branch on a production site right now. It's
nothing major, a volunteer organization with minimal needs, but for my
limited uses, it is worki
Hi Nick,
On Thu, 2006-10-19 at 18:48 -0700, [EMAIL PROTECTED] wrote:
> Malcolm ,
> Thanks for you for your contributions, your presence on this project
> really makes a positive difference.
>
> > It's already "ready" and able to be used. Chris keeps his branch in sync
> > with trunk regularly
Malcolm ,
Thanks for you for your contributions, your presence on this project
really makes a positive difference.
> It's already "ready" and able to be used. Chris keeps his branch in sync
> with trunk regularly and is extremely responsive to fixing bugs. It will
> be merged when we have had a
> here is what I hear you saying.
>
> you'd rather write your own code to do the same/similar thing to what
> chris
> has already done (and also what has a high chance of getting merged
> in the
> coming months).
What I'm trying to say, is that I was working to implement something
that wouldn't i
On Thu, 2006-10-19 at 16:40 -0700, Noah wrote:
> This sort of thing is asked for time and time again, is there any idea
> when Chris' code will be ready?
It's already "ready" and able to be used. Chris keeps his branch in sync
with trunk regularly and is extremely responsive to fixing bugs. It wi
This sort of thing is asked for time and time again, is there any idea
when Chris' code will be ready?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to djang
On 20/10/2006, at 9:01 AM, [EMAIL PROTECTED] wrote:
>
> Hi Ian,
> This is very similar to what Chris has done. The issue is that his
> code hasn't been merged with Trunk, which puts me in an awkward
> position in terms of adopting it for something that is outside the
> scope of a test applica
Hi Ian,
This is very similar to what Chris has done. The issue is that his
code hasn't been merged with Trunk, which puts me in an awkward
position in terms of adopting it for something that is outside the
scope of a test application. I started working on a solution to this
problem a few month
Hi Nick.
can you tell me how this is different that the stuff Chris Long
worked on in his branch?
It seems very similar.
regards
Ian.
On 20/10/2006, at 6:24 AM, [EMAIL PROTECTED] wrote:
>
> Note: I have tried to post this two other time, but the thread wasn't
> added to the group. I apologi
Note: I have tried to post this two other time, but the thread wasn't
added to the group. I apologize if this shows up multiple times on the
list. I just want to make sure that it's being sent out.
--
12 matches
Mail list logo
