Login | Register
My pages Projects Community openCollabNet

Discussions > dev > [propel-dev] NestSet 1.3 branch merge

propel
Discussion topic

Hide all messages in topic

All messages in topic

Re: [propel-dev] NestSet 1.3 branch merge

Reply

Author =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com>
Full name =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com>
Date 2007-11-03 18:01:52 PDT
Message Did some testing, and looks good so far, but I think I'll do this
tomorrow at the conf, so Hans has the option to slap me right away if
I mess something up ;)


- David



Am 03.11.2007 um 21:55 schrieb David Zülke:

> Didn't :) Synced again. Dominik and I will perform some tests if any
> of the 1.3 stuff added in between causes wonkiness, and after that,
> I'll do the merge.
>
>
> David
>
>
>
> Am 03.11.2007 um 18:06 schrieb Hans Lellelid:
>
>> Hi David,
>>
>> Yeah, I keep committing new small changes to 1.3. Just to piss you
>> off
>> :) I don't expect that'll matter for your merge, though.
>>
>> Hans
>>
>> David Zülke wrote:
>>> "my" branch and 1.3 are in sync now. I gotta run now (shopping!),
>>> but I
>>> will merge my branch to 1.3 later in the evening.
>>>
>>>
>>> David
>>>
>>>
>>>
>>>
>>> Am 03.11.2007 um 17:01 schrieb Hans Lellelid:
>>>
>>>> Sounds like fun. :) I'm going to probably work on a few Propel
>>>> 1.3 bugs
>>>> too, but I'll avoid doing something like a code style cleanup on
>>>> the
>>>> builder classes ;)
>>>>
>>>> David Zülke wrote:
>>>>> Going through all changes right now to merge critical stuff by
>>>>> hand,
>>>>> but that takes some time. I also need to roll Agavi 0.11.0 later
>>>>> today
>>>>> and do some shopping, but I hope I can finish this today ;)
>>>>>
>>>>> David
>>>>>
>>>>>
>>>>>
>>>>> Am 03.11.2007 um 11:04 schrieb Eric Fredj:
>>>>>
>>>>>> No pb :-)
>>>>>>
>>>>>> I know what busy means :-D
>>>>>>
>>>>>> Heltem
>>>>>>
>>>>>> David Zülke a écrit :
>>>>>>> Sorry, sorry, I'll really get to this tomorrow (otherwise,
>>>>>>> Hans will
>>>>>>> be allowed to slap me in the face when we meet at the
>>>>>>> conference). I
>>>>>>> really have a strong interest in getting this merged, so no
>>>>>>> worries ;)
>>>>>>> Sorry for the holdup.
>>>>>>>
>>>>>>> David
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Am 02.11.2007 um 20:18 schrieb Eric Fredj:
>>>>>>>
>>>>>​>>> Hi,
>>>>>​>>>
>>>>>​>>> Anyone sees any problem with the merge between heltem/ and 1.3/
>>>>>​>>>
>>>>>​>>> David ?
>>>>>​>>>
>>>>>​>>> Eric Fredj a écrit :
>>>>>​>>>> Did someone have time to see if multi-nestedset can be
>>>>>​>>>> merged in 1.3
>>>>>​>>>> (david-multi_nested_set_tables/ or heltem/ branch) ?
>>>>>​>>>>
>>>>>​>>>> I really think we should merge multi-nestedset support.
>>>>>​>>>>
>>>>>​>>>> David > If you prefer, you can merge your branch and then I
>>>>>​>>>> will
>>>>>​>>>> apply
>>>>>​>>>> my diff changes
>>>>>​>>>>
>>>>>​>>>> Regards,
>>>>>​>>>>
>>>>>​>>>> Heltem
>>>>>>
>>>>>> --------------------​--------------------​--------------------​---------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
>>>>>> For additional commands, e-mail: dev-help at propel dot tigris dot org
>>>>>>
>>>>>>
>>>>>
>>>>> --------------------​--------------------​--------------------​---------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
>>>>> For additional commands, e-mail: dev-help at propel dot tigris dot org
>>>>>
>>>>
>>>> --------------------​--------------------​--------------------​---------
>>>> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
>>>> For additional commands, e-mail: dev-help at propel dot tigris dot org
>>>>
>>>>
>>>
>>> --------------------​--------------------​--------------------​---------
>>> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
>>> For additional commands, e-mail: dev-help at propel dot tigris dot org
>>>
>>
>> --------------------​--------------------​--------------------​---------
>> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
>> For additional commands, e-mail: dev-help at propel dot tigris dot org
>>
>>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
> For additional commands, e-mail: dev-help at propel dot tigris dot org
>
>

Re: [propel-dev] NestSet 1.3 branch merge

Reply

Author =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com>
Full name =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com>
Date 2007-11-03 13:55:15 PDT
Message Didn't :) Synced again. Dominik and I will perform some tests if any
of the 1.3 stuff added in between causes wonkiness, and after that,
I'll do the merge.


David



Am 03.11.2007 um 18:06 schrieb Hans Lellelid:

> Hi David,
>
> Yeah, I keep committing new small changes to 1.3. Just to piss you
> off
> :) I don't expect that'll matter for your merge, though.
>
> Hans
>
> David Zülke wrote:
>> "my" branch and 1.3 are in sync now. I gotta run now (shopping!),
>> but I
>> will merge my branch to 1.3 later in the evening.
>>
>>
>> David
>>
>>
>>
>>
>> Am 03.11.2007 um 17:01 schrieb Hans Lellelid:
>>
>>> Sounds like fun. :) I'm going to probably work on a few Propel
>>> 1.3 bugs
>>> too, but I'll avoid doing something like a code style cleanup on the
>>> builder classes ;)
>>>
>>> David Zülke wrote:
>>>> Going through all changes right now to merge critical stuff by
>>>> hand,
>>>> but that takes some time. I also need to roll Agavi 0.11.0 later
>>>> today
>>>> and do some shopping, but I hope I can finish this today ;)
>>>>
>>>> David
>>>>
>>>>
>>>>
>>>> Am 03.11.2007 um 11:04 schrieb Eric Fredj:
>>>>
>>>>> No pb :-)
>>>>>
>>>>> I know what busy means :-D
>>>>>
>>>>> Heltem
>>>>>
>>>>> David Zülke a écrit :
>>>>>> Sorry, sorry, I'll really get to this tomorrow (otherwise, Hans
>>>>>> will
>>>>>> be allowed to slap me in the face when we meet at the
>>>>>> conference). I
>>>>>> really have a strong interest in getting this merged, so no
>>>>>> worries ;)
>>>>>> Sorry for the holdup.
>>>>>>
>>>>>> David
>>>>>>
>>>>>>
>>>>>>
>>>>>> Am 02.11.2007 um 20:18 schrieb Eric Fredj:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> Anyone sees any problem with the merge between heltem/ and 1.3/
>>>>>>>
>>>>>>> David ?
>>>>>>>
>>>>>>> Eric Fredj a écrit :
>>>>>​>>> Did someone have time to see if multi-nestedset can be merged
>>>>>​>>> in 1.3
>>>>>​>>> (david-multi_nested_set_tables/ or heltem/ branch) ?
>>>>>​>>>
>>>>>​>>> I really think we should merge multi-nestedset support.
>>>>>​>>>
>>>>>​>>> David > If you prefer, you can merge your branch and then I
>>>>>​>>> will
>>>>>​>>> apply
>>>>>​>>> my diff changes
>>>>>​>>>
>>>>>​>>> Regards,
>>>>>​>>>
>>>>>​>>> Heltem
>>>>>
>>>>> --------------------​--------------------​--------------------​---------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
>>>>> For additional commands, e-mail: dev-help at propel dot tigris dot org
>>>>>
>>>>>
>>>>
>>>> --------------------​--------------------​--------------------​---------
>>>> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
>>>> For additional commands, e-mail: dev-help at propel dot tigris dot org
>>>>
>>>
>>> --------------------​--------------------​--------------------​---------
>>> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
>>> For additional commands, e-mail: dev-help at propel dot tigris dot org
>>>
>>>
>>
>> --------------------​--------------------​--------------------​---------
>> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
>> For additional commands, e-mail: dev-help at propel dot tigris dot org
>>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
> For additional commands, e-mail: dev-help at propel dot tigris dot org
>
>

Re: [propel-dev] NestSet 1.3 branch merge

Reply

Author hlellelid
Full name Hans Lellelid
Date 2007-11-03 10:06:51 PDT
Message Hi David,

Yeah, I keep committing new small changes to 1.3. Just to piss you off
:) I don't expect that'll matter for your merge, though.

Hans

David Zülke wrote:
> "my" branch and 1.3 are in sync now. I gotta run now (shopping!), but I
> will merge my branch to 1.3 later in the evening.
>
>
> David
>
>
>
>
> Am 03.11.2007 um 17:01 schrieb Hans Lellelid:
>
>> Sounds like fun. :) I'm going to probably work on a few Propel 1.3 bugs
>> too, but I'll avoid doing something like a code style cleanup on the
>> builder classes ;)
>>
>> David Zülke wrote:
>>> Going through all changes right now to merge critical stuff by hand,
>>> but that takes some time. I also need to roll Agavi 0.11.0 later today
>>> and do some shopping, but I hope I can finish this today ;)
>>>
>>> David
>>>
>>>
>>>
>>> Am 03.11.2007 um 11:04 schrieb Eric Fredj:
>>>
>>>> No pb :-)
>>>>
>>>> I know what busy means :-D
>>>>
>>>> Heltem
>>>>
>>>> David Zülke a écrit :
>>>>> Sorry, sorry, I'll really get to this tomorrow (otherwise, Hans will
>>>>> be allowed to slap me in the face when we meet at the conference). I
>>>>> really have a strong interest in getting this merged, so no worries ;)
>>>>> Sorry for the holdup.
>>>>>
>>>>> David
>>>>>
>>>>>
>>>>>
>>>>> Am 02.11.2007 um 20:18 schrieb Eric Fredj:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Anyone sees any problem with the merge between heltem/ and 1.3/
>>>>>>
>>>>>> David ?
>>>>>>
>>>>>> Eric Fredj a écrit :
>>>>>>> Did someone have time to see if multi-nestedset can be merged in 1.3
>>>>>>> (david-multi_nested_set_tables/ or heltem/ branch) ?
>>>>>>>
>>>>>>> I really think we should merge multi-nestedset support.
>>>>>>>
>>>>>>> David > If you prefer, you can merge your branch and then I will
>>>>>>> apply
>>>>>>> my diff changes
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Heltem
>>>>
>>>> --------------------​--------------------​--------------------​---------
>>>> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
>>>> For additional commands, e-mail: dev-help at propel dot tigris dot org
>>>>
>>>>
>>>
>>> --------------------​--------------------​--------------------​---------
>>> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
>>> For additional commands, e-mail: dev-help at propel dot tigris dot org
>>>
>>
>> --------------------​--------------------​--------------------​---------
>> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
>> For additional commands, e-mail: dev-help at propel dot tigris dot org
>>
>>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
> For additional commands, e-mail: dev-help at propel dot tigris dot org
>

Re: [propel-dev] NestSet 1.3 branch merge

Reply

Author =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com>
Full name =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com>
Date 2007-11-03 09:40:29 PDT
Message "my" branch and 1.3 are in sync now. I gotta run now (shopping!), but
I will merge my branch to 1.3 later in the evening.


David




Am 03.11.2007 um 17:01 schrieb Hans Lellelid:

> Sounds like fun. :) I'm going to probably work on a few Propel 1.3
> bugs
> too, but I'll avoid doing something like a code style cleanup on the
> builder classes ;)
>
> David Zülke wrote:
>> Going through all changes right now to merge critical stuff by hand,
>> but that takes some time. I also need to roll Agavi 0.11.0 later
>> today
>> and do some shopping, but I hope I can finish this today ;)
>>
>> David
>>
>>
>>
>> Am 03.11.2007 um 11:04 schrieb Eric Fredj:
>>
>>> No pb :-)
>>>
>>> I know what busy means :-D
>>>
>>> Heltem
>>>
>>> David Zülke a écrit :
>>>> Sorry, sorry, I'll really get to this tomorrow (otherwise, Hans
>>>> will
>>>> be allowed to slap me in the face when we meet at the
>>>> conference). I
>>>> really have a strong interest in getting this merged, so no
>>>> worries ;)
>>>> Sorry for the holdup.
>>>>
>>>> David
>>>>
>>>>
>>>>
>>>> Am 02.11.2007 um 20:18 schrieb Eric Fredj:
>>>>
>>>>> Hi,
>>>>>
>>>>> Anyone sees any problem with the merge between heltem/ and 1.3/
>>>>>
>>>>> David ?
>>>>>
>>>>> Eric Fredj a écrit :
>>>>>> Did someone have time to see if multi-nestedset can be merged
>>>>>> in 1.3
>>>>>> (david-multi_nested_set_tables/ or heltem/ branch) ?
>>>>>>
>>>>>> I really think we should merge multi-nestedset support.
>>>>>>
>>>>>> David > If you prefer, you can merge your branch and then I will
>>>>>> apply
>>>>>> my diff changes
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Heltem
>>>
>>> --------------------​--------------------​--------------------​---------
>>> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
>>> For additional commands, e-mail: dev-help at propel dot tigris dot org
>>>
>>>
>>
>> --------------------​--------------------​--------------------​---------
>> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
>> For additional commands, e-mail: dev-help at propel dot tigris dot org
>>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
> For additional commands, e-mail: dev-help at propel dot tigris dot org
>
>

Re: [propel-dev] NestSet 1.3 branch merge

Reply

Author hlellelid
Full name Hans Lellelid
Date 2007-11-03 09:01:47 PDT
Message Sounds like fun. :) I'm going to probably work on a few Propel 1.3 bugs
too, but I'll avoid doing something like a code style cleanup on the
builder classes ;)

David Zülke wrote:
> Going through all changes right now to merge critical stuff by hand,
> but that takes some time. I also need to roll Agavi 0.11.0 later today
> and do some shopping, but I hope I can finish this today ;)
>
> David
>
>
>
> Am 03.11.2007 um 11:04 schrieb Eric Fredj:
>
>> No pb :-)
>>
>> I know what busy means :-D
>>
>> Heltem
>>
>> David Zülke a écrit :
>>> Sorry, sorry, I'll really get to this tomorrow (otherwise, Hans will
>>> be allowed to slap me in the face when we meet at the conference). I
>>> really have a strong interest in getting this merged, so no worries ;)
>>> Sorry for the holdup.
>>>
>>> David
>>>
>>>
>>>
>>> Am 02.11.2007 um 20:18 schrieb Eric Fredj:
>>>
>>>> Hi,
>>>>
>>>> Anyone sees any problem with the merge between heltem/ and 1.3/
>>>>
>>>> David ?
>>>>
>>>> Eric Fredj a écrit :
>>>>> Did someone have time to see if multi-nestedset can be merged in 1.3
>>>>> (david-multi_nested_set_tables/ or heltem/ branch) ?
>>>>>
>>>>> I really think we should merge multi-nestedset support.
>>>>>
>>>>> David > If you prefer, you can merge your branch and then I will
>>>>> apply
>>>>> my diff changes
>>>>>
>>>>> Regards,
>>>>>
>>>>> Heltem
>>
>> --------------------​--------------------​--------------------​---------
>> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
>> For additional commands, e-mail: dev-help at propel dot tigris dot org
>>
>>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
> For additional commands, e-mail: dev-help at propel dot tigris dot org
>

Re: [propel-dev] NestSet 1.3 branch merge

Reply

Author =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com>
Full name =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com>
Date 2007-11-03 09:00:40 PDT
Message Going through all changes right now to merge critical stuff by hand,
but that takes some time. I also need to roll Agavi 0.11.0 later today
and do some shopping, but I hope I can finish this today ;)

David



Am 03.11.2007 um 11:04 schrieb Eric Fredj:

> No pb :-)
>
> I know what busy means :-D
>
> Heltem
>
> David Zülke a écrit :
>> Sorry, sorry, I'll really get to this tomorrow (otherwise, Hans will
>> be allowed to slap me in the face when we meet at the conference). I
>> really have a strong interest in getting this merged, so no
>> worries ;)
>> Sorry for the holdup.
>>
>> David
>>
>>
>>
>> Am 02.11.2007 um 20:18 schrieb Eric Fredj:
>>
>>> Hi,
>>>
>>> Anyone sees any problem with the merge between heltem/ and 1.3/
>>>
>>> David ?
>>>
>>> Eric Fredj a écrit :
>>>> Did someone have time to see if multi-nestedset can be merged in
>>>> 1.3
>>>> (david-multi_nested_set_tables/ or heltem/ branch) ?
>>>>
>>>> I really think we should merge multi-nestedset support.
>>>>
>>>> David > If you prefer, you can merge your branch and then I will
>>>> apply
>>>> my diff changes
>>>>
>>>> Regards,
>>>>
>>>> Heltem
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
> For additional commands, e-mail: dev-help at propel dot tigris dot org
>
>

Re: [propel-dev] NestSet 1.3 branch merge

Reply

Author hlellelid
Full name Hans Lellelid
Date 2007-11-03 08:50:24 PDT
Message Excellent! -- Sorry, I didn't even think to check the history there :)

Hans

Eric Fredj wrote:
> Yes, you're right and I was updating wiki for that since this morning :-)
> I refactored NestedSet pages and all tree management pages.
>
> Heltem
>
> Hans Lellelid a écrit :
>
>> Hi Eric (& David) --
>>
>> While you're updating this stuff, can you also make any necessary
>> changes to the nested set docs on the wiki? I assume those are still
>> correct, just want to make sure, since I don't think there's any other
>> instruction for telling folks how to use this stuff.
>>
>> Thanks guys!
>>
>> Hans
>>
>> Eric Fredj wrote:
>>
>>
>>> No pb :-)
>>>
>>> I know what busy means :-D
>>>
>>> Heltem
>>>
>>> David Zülke a écrit :
>>>
>>>
>>>
>>>> Sorry, sorry, I'll really get to this tomorrow (otherwise, Hans will
>>>> be allowed to slap me in the face when we meet at the conference). I
>>>> really have a strong interest in getting this merged, so no worries ;)
>>>> Sorry for the holdup.
>>>>
>>>> David
>>>>
>>>>
>>>>
>>>> Am 02.11.2007 um 20:18 schrieb Eric Fredj:
>>>>
>>>>
>>>>
>>>>
>>>>> Hi,
>>>>>
>>>>> Anyone sees any problem with the merge between heltem/ and 1.3/
>>>>>
>>>>> David ?
>>>>>
>>>>> Eric Fredj a écrit :
>>>>>
>>>>>
>>>>>
>>>>>> Did someone have time to see if multi-nestedset can be merged in 1.3
>>>>>> (david-multi_nested_set_tables/ or heltem/ branch) ?
>>>>>>
>>>>>> I really think we should merge multi-nestedset support.
>>>>>>
>>>>>> David > If you prefer, you can merge your branch and then I will apply
>>>>>> my diff changes
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Heltem
>>>>>>
>>>>>>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
> For additional commands, e-mail: dev-help at propel dot tigris dot org
>
>

Re: [propel-dev] NestSet 1.3 branch merge

Reply

Author Eric Fredj <eofredj at gmail dot com>
Full name Eric Fredj <eofredj at gmail dot com>
Date 2007-11-03 08:49:03 PDT
Message Yes, you're right and I was updating wiki for that since this morning :-)
I refactored NestedSet pages and all tree management pages.

Heltem

Hans Lellelid a écrit :
> Hi Eric (& David) --
>
> While you're updating this stuff, can you also make any necessary
> changes to the nested set docs on the wiki? I assume those are still
> correct, just want to make sure, since I don't think there's any other
> instruction for telling folks how to use this stuff.
>
> Thanks guys!
>
> Hans
>
> Eric Fredj wrote:
>
>> No pb :-)
>>
>> I know what busy means :-D
>>
>> Heltem
>>
>> David Zülke a écrit :
>>
>>
>>> Sorry, sorry, I'll really get to this tomorrow (otherwise, Hans will
>>> be allowed to slap me in the face when we meet at the conference). I
>>> really have a strong interest in getting this merged, so no worries ;)
>>> Sorry for the holdup.
>>>
>>> David
>>>
>>>
>>>
>>> Am 02.11.2007 um 20:18 schrieb Eric Fredj:
>>>
>>>
>>>
>>>> Hi,
>>>>
>>>> Anyone sees any problem with the merge between heltem/ and 1.3/
>>>>
>>>> David ?
>>>>
>>>> Eric Fredj a écrit :
>>>>
>>>>
>>>>> Did someone have time to see if multi-nestedset can be merged in 1.3
>>>>> (david-multi_nested_set_tables/ or heltem/ branch) ?
>>>>>
>>>>> I really think we should merge multi-nestedset support.
>>>>>
>>>>> David > If you prefer, you can merge your branch and then I will apply
>>>>> my diff changes
>>>>>
>>>>> Regards,
>>>>>
>>>>> Heltem
>>>>>

Re: [propel-dev] NestSet 1.3 branch merge

Reply

Author hlellelid
Full name Hans Lellelid
Date 2007-11-03 08:36:24 PDT
Message Hi Eric (& David) --

While you're updating this stuff, can you also make any necessary
changes to the nested set docs on the wiki? I assume those are still
correct, just want to make sure, since I don't think there's any other
instruction for telling folks how to use this stuff.

Thanks guys!

Hans

Eric Fredj wrote:
> No pb :-)
>
> I know what busy means :-D
>
> Heltem
>
> David Zülke a écrit :
>
>> Sorry, sorry, I'll really get to this tomorrow (otherwise, Hans will
>> be allowed to slap me in the face when we meet at the conference). I
>> really have a strong interest in getting this merged, so no worries ;)
>> Sorry for the holdup.
>>
>> David
>>
>>
>>
>> Am 02.11.2007 um 20:18 schrieb Eric Fredj:
>>
>>
>>> Hi,
>>>
>>> Anyone sees any problem with the merge between heltem/ and 1.3/
>>>
>>> David ?
>>>
>>> Eric Fredj a écrit :
>>>
>>>> Did someone have time to see if multi-nestedset can be merged in 1.3
>>>> (david-multi_nested_set_tables/ or heltem/ branch) ?
>>>>
>>>> I really think we should merge multi-nestedset support.
>>>>
>>>> David > If you prefer, you can merge your branch and then I will apply
>>>> my diff changes
>>>>
>>>> Regards,
>>>>
>>>> Heltem
>>>>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
> For additional commands, e-mail: dev-help at propel dot tigris dot org
>
>

Re: [propel-dev] NestSet 1.3 branch merge

Reply

Author Eric Fredj <eofredj at gmail dot com>
Full name Eric Fredj <eofredj at gmail dot com>
Date 2007-11-03 03:04:21 PDT
Message No pb :-)

I know what busy means :-D

Heltem

David Zülke a écrit :
> Sorry, sorry, I'll really get to this tomorrow (otherwise, Hans will
> be allowed to slap me in the face when we meet at the conference). I
> really have a strong interest in getting this merged, so no worries ;)
> Sorry for the holdup.
>
> David
>
>
>
> Am 02.11.2007 um 20:18 schrieb Eric Fredj:
>
>> Hi,
>>
>> Anyone sees any problem with the merge between heltem/ and 1.3/
>>
>> David ?
>>
>> Eric Fredj a écrit :
>>> Did someone have time to see if multi-nestedset can be merged in 1.3
>>> (david-multi_nested_set_tables/ or heltem/ branch) ?
>>>
>>> I really think we should merge multi-nestedset support.
>>>
>>> David > If you prefer, you can merge your branch and then I will apply
>>> my diff changes
>>>
>>> Regards,
>>>
>>> Heltem

Re: [propel-dev] NestSet 1.3 branch merge

Reply

Author =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com>
Full name =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com>
Date 2007-11-02 14:03:03 PDT
Message Sorry, sorry, I'll really get to this tomorrow (otherwise, Hans will
be allowed to slap me in the face when we meet at the conference). I
really have a strong interest in getting this merged, so no worries ;)
Sorry for the holdup.

David



Am 02.11.2007 um 20:18 schrieb Eric Fredj:

> Hi,
>
> Anyone sees any problem with the merge between heltem/ and 1.3/
>
> David ?
>
> Eric Fredj a écrit :
>> Did someone have time to see if multi-nestedset can be merged in 1.3
>> (david-multi_nested_set_tables/ or heltem/ branch) ?
>>
>> I really think we should merge multi-nestedset support.
>>
>> David > If you prefer, you can merge your branch and then I will
>> apply
>> my diff changes
>>
>> Regards,
>>
>> Heltem
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
> For additional commands, e-mail: dev-help at propel dot tigris dot org
>
>

Re: [propel-dev] NestSet 1.3 branch merge

Reply

Author Eric Fredj <eofredj at gmail dot com>
Full name Eric Fredj <eofredj at gmail dot com>
Date 2007-11-02 12:18:04 PDT
Message Hi,

Anyone sees any problem with the merge between heltem/ and 1.3/

David ?

Eric Fredj a écrit :
> Did someone have time to see if multi-nestedset can be merged in 1.3
> (david-multi_nested_set_tables/ or heltem/ branch) ?
>
> I really think we should merge multi-nestedset support.
>
> David > If you prefer, you can merge your branch and then I will apply
> my diff changes
>
> Regards,
>
> Heltem

Re: [propel-dev] NestSet 1.3 branch merge

Reply

Author Eric Fredj <eofredj at gmail dot com>
Full name Eric Fredj <eofredj at gmail dot com>
Date 2007-10-30 05:44:48 PDT
Message Did someone have time to see if multi-nestedset can be merged in 1.3
(david-multi_nested_set_tables/ or heltem/ branch) ?

I really think we should merge multi-nestedset support.

David > If you prefer, you can merge your branch and then I will apply
my diff changes

Regards,

Heltem

Re: [propel-dev] NestSet 1.3 branch merge

Reply

Author Eric Fredj <eofredj at gmail dot com>
Full name Eric Fredj <eofredj at gmail dot com>
Date 2007-10-28 04:39:16 PDT
Message David Zülke a écrit :
> Okay... but I don't think we should start changing things just so it
> fits symfony more nicely. I don't remember changing method names in my
> branch, and we should keep it like that.
>
>
> David
My aim was not to fit symfony but to get good ideas/implementations they
added to ours.
I tried to make this smartly.
I think we can get mutual benefits with each other. For that matter, I
proposed fix to their implementation.

I hope you will agree with my changes.

ErIC

Re: [propel-dev] NestSet 1.3 branch merge

Reply

Author Eric Fredj <eofredj at gmail dot com>
Full name Eric Fredj <eofredj at gmail dot com>
Date 2007-10-28 04:33:50 PDT
Message Ok.
I will explain my strategy.
I branch 1.3/ to heltem/ and then I applied all
david-multi_nested_set_tables/ branch changes on heltem/ to make easy
the future. merge

However, I saw many things which were buggy so I fixed some of them.

About sfPropel .... Plugin API, they got our API and added some methods
which made sense to me (insertAsParentOf(), ..) , so I integrated them
and some of ours was not yet implemented or were unuseful so I removed them.
And I added a parent attribute which made sense to me to simplify some
of our methods.

Moreover, I cleaned most of modifiers (static, public, etc.)

If you make a diff between yours and mine, I think changes are really
light and most of them are about 1.3 merge ....

I think the task now is to merge heltem/ and 1.3
Here is attached the patch for that.

My goal was really to make your merge task easy, David.

David Zülke a écrit :
> Okay... but I don't think we should start changing things just so it
> fits symfony more nicely. I don't remember changing method names in my
> branch, and we should keep it like that.
>
>
> David

Re: [propel-dev] NestSet 1.3 branch merge

Reply

Author =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com>
Full name =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com>
Date 2007-10-28 03:57:10 PDT
Message Okay... but I don't think we should start changing things just so it
fits symfony more nicely. I don't remember changing method names in my
branch, and we should keep it like that.


David



Am 28.10.2007 um 08:29 schrieb Frank Stelzer:

> Just a small explanation to sfPropelActAsNestedS​etBehaviourPlugin (http://trac.symfony-​project.com/wiki/sfP​ropelActAsNestedSetB​ehaviorPlugin
> , if someone wonders about this term):
>
> sfPropel*Behaviour is the possibility to add some methods of a
> special domain to the model classes.
>
>
> Through the sfPropelActAsNestedS​etBehaviourPlugin you can add nested
> set support to model classes (through a magic __call method you can
> call methods of special behaviour, which were registered in your
> project). Symfony uses for version <= 1.0.x Propel 1.2 and so this
> behaviour was needed to have any nested set support.
>
>
> The methods naming of sfPropelActAsNestedS​etBehaviorPlugin and
> Propel 1.3 nested set support is mostly the same.
>
>
>
> Am 28.10.2007 um 03:42 schrieb David Zülke:
>
>> Errr... why didn't you branch off my branch? Now things are gonna
>> be complicated.
>>
>> Also, I don't get this whole sfPropelActAsNestedS​etBehaviourPlugin
>> stuff, care to explain?
>>
>>
>> David
>>
>>
>>
>>
>> Am 26.10.2007 um 14:06 schrieb Eric Fredj:
>>
>>> I created a /heltem /branch to commit my Nestedset changes to avoid
>>> conflict on your branch if you planned some changes on it before
>>> merge
>>> in 1.3.
>>>
>>> That way, users can test my changes easily.
>>>
>>> I am currently working in sfPropelActAsNestedS​etBehaviourPlugin
>>> port to
>>> Propel core to support it natively.
>>>
>>> Regards,
>>> Heltem
>>>
>>> Eric Fredj a écrit :
>>>> Integrated PropelPDO in node runtime classes and builders too ;-)
>>>>
>>>> Eric Fredj a écrit :
>>>>
>>>>> David,
>>>>>
>>>>> I made a merge for 1.3 branch and yours on my dev host.
>>>>> I will submit it to you before commit it.
>>>>> I applied all david-multi_nested_set_tables changes and some of
>>>>> mine on 1.3.
>>>>>
>>>>> Moreover, I tried to follow API defined in
>>>>> sfPropelActAsNestedS​etBehaviorPlugin ...
>>>>>
>>>>> Waiting for your feedback. :-)
>>>>>
>>>>> Patch is attached.
>>>>>
>>>>> Regards,
>>>>> Heltem
>>>>>
>>>
>>> --------------------​--------------------​--------------------​---------
>>> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
>>> For additional commands, e-mail: dev-help at propel dot tigris dot org
>>>
>>>
>>
>> --------------------​--------------------​--------------------​---------
>> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
>> For additional commands, e-mail: dev-help at propel dot tigris dot org
>>
>>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
> For additional commands, e-mail: dev-help at propel dot tigris dot org
>
>

Re: [propel-dev] NestSet 1.3 branch merge

Reply

Author Frank Stelzer <dev at bleedingmoon dot de>
Full name Frank Stelzer <dev at bleedingmoon dot de>
Date 2007-10-28 00:29:48 PDT
Message Just a small explanation to sfPropelActAsNestedS​etBehaviourPlugin
(http://trac.symfony-​project.com/wiki/
sfPropelActAsNestedS​etBehaviorPlugin, if someone wonders about this
term):

sfPropel*Behaviour is the possibility to add some methods of a
special domain to the model classes.


Through the sfPropelActAsNestedS​etBehaviourPlugin you can add nested
set support to model classes (through a magic __call method you can
call methods of special behaviour, which were registered in your
project). Symfony uses for version <= 1.0.x Propel 1.2 and so this
behaviour was needed to have any nested set support.


The methods naming of sfPropelActAsNestedS​etBehaviorPlugin and Propel
1.3 nested set support is mostly the same.



Am 28.10.2007 um 03:42 schrieb David Zülke:

> Errr... why didn't you branch off my branch? Now things are gonna
> be complicated.
>
> Also, I don't get this whole sfPropelActAsNestedS​etBehaviourPlugin
> stuff, care to explain?
>
>
> David
>
>
>
>
> Am 26.10.2007 um 14:06 schrieb Eric Fredj:
>
>> I created a /heltem /branch to commit my Nestedset changes to avoid
>> conflict on your branch if you planned some changes on it before
>> merge
>> in 1.3.
>>
>> That way, users can test my changes easily.
>>
>> I am currently working in sfPropelActAsNestedS​etBehaviourPlugin
>> port to
>> Propel core to support it natively.
>>
>> Regards,
>> Heltem
>>
>> Eric Fredj a écrit :
>>> Integrated PropelPDO in node runtime classes and builders too ;-)
>>>
>>> Eric Fredj a écrit :
>>>
>>>> David,
>>>>
>>>> I made a merge for 1.3 branch and yours on my dev host.
>>>> I will submit it to you before commit it.
>>>> I applied all david-multi_nested_set_tables changes and some of
>>>> mine on 1.3.
>>>>
>>>> Moreover, I tried to follow API defined in
>>>> sfPropelActAsNestedS​etBehaviorPlugin ...
>>>>
>>>> Waiting for your feedback. :-)
>>>>
>>>> Patch is attached.
>>>>
>>>> Regards,
>>>> Heltem
>>>>
>>
>> --------------------​--------------------​--------------------​---------
>> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
>> For additional commands, e-mail: dev-help at propel dot tigris dot org
>>
>>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
> For additional commands, e-mail: dev-help at propel dot tigris dot org
>
>

Re: [propel-dev] NestSet 1.3 branch merge

Reply

Author =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com>
Full name =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com>
Date 2007-10-27 20:37:26 PDT
Message yeah but I think he branched 1.3, then applied the patch he sent which
seems to be a merge of my branch to 1.3 plus custom stuff... that's
gonna make things pretty complicated to merge, especially when syncing
changes. I don't really get it, but I'll just merge my branch in
tomorrow as planned :p

David



Am 28.10.2007 um 04:11 schrieb Hans Lellelid:

> I was confused by that branch off of the branch too :) I guess Eric
> just wants to keep you in tip-top SVN merge shape :)
>
> Hans
>
> David Zülke wrote:
>> Errr... why didn't you branch off my branch? Now things are gonna be
>> complicated.
>>
>> Also, I don't get this whole sfPropelActAsNestedS​etBehaviourPlugin
>> stuff, care to explain?
>>
>>
>> David
>>
>>
>>
>>
>> Am 26.10.2007 um 14:06 schrieb Eric Fredj:
>>
>>> I created a /heltem /branch to commit my Nestedset changes to avoid
>>> conflict on your branch if you planned some changes on it before
>>> merge
>>> in 1.3.
>>>
>>> That way, users can test my changes easily.
>>>
>>> I am currently working in sfPropelActAsNestedS​etBehaviourPlugin
>>> port to
>>> Propel core to support it natively.
>>>
>>> Regards,
>>> Heltem
>>>
>>> Eric Fredj a écrit :
>>>> Integrated PropelPDO in node runtime classes and builders too ;-)
>>>>
>>>> Eric Fredj a écrit :
>>>>
>>>>> David,
>>>>>
>>>>> I made a merge for 1.3 branch and yours on my dev host.
>>>>> I will submit it to you before commit it.
>>>>> I applied all david-multi_nested_set_tables changes and some of
>>>>> mine
>>>>> on 1.3.
>>>>>
>>>>> Moreover, I tried to follow API defined in
>>>>> sfPropelActAsNestedS​etBehaviorPlugin ...
>>>>>
>>>>> Waiting for your feedback. :-)
>>>>>
>>>>> Patch is attached.
>>>>>
>>>>> Regards,
>>>>> Heltem
>>>>>
>>>
>>> --------------------​--------------------​--------------------​---------
>>> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
>>> For additional commands, e-mail: dev-help at propel dot tigris dot org
>>>
>>>
>>
>> --------------------​--------------------​--------------------​---------
>> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
>> For additional commands, e-mail: dev-help at propel dot tigris dot org
>>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
> For additional commands, e-mail: dev-help at propel dot tigris dot org
>
>

Re: [propel-dev] NestSet 1.3 branch merge

Reply

Author hlellelid
Full name Hans Lellelid
Date 2007-10-27 20:11:42 PDT
Message I was confused by that branch off of the branch too :) I guess Eric
just wants to keep you in tip-top SVN merge shape :)

Hans

David Zülke wrote:
> Errr... why didn't you branch off my branch? Now things are gonna be
> complicated.
>
> Also, I don't get this whole sfPropelActAsNestedS​etBehaviourPlugin
> stuff, care to explain?
>
>
> David
>
>
>
>
> Am 26.10.2007 um 14:06 schrieb Eric Fredj:
>
>> I created a /heltem /branch to commit my Nestedset changes to avoid
>> conflict on your branch if you planned some changes on it before merge
>> in 1.3.
>>
>> That way, users can test my changes easily.
>>
>> I am currently working in sfPropelActAsNestedS​etBehaviourPlugin port to
>> Propel core to support it natively.
>>
>> Regards,
>> Heltem
>>
>> Eric Fredj a écrit :
>>> Integrated PropelPDO in node runtime classes and builders too ;-)
>>>
>>> Eric Fredj a écrit :
>>>
>>>> David,
>>>>
>>>> I made a merge for 1.3 branch and yours on my dev host.
>>>> I will submit it to you before commit it.
>>>> I applied all david-multi_nested_set_tables changes and some of mine
>>>> on 1.3.
>>>>
>>>> Moreover, I tried to follow API defined in
>>>> sfPropelActAsNestedS​etBehaviorPlugin ...
>>>>
>>>> Waiting for your feedback. :-)
>>>>
>>>> Patch is attached.
>>>>
>>>> Regards,
>>>> Heltem
>>>>
>>
>> --------------------​--------------------​--------------------​---------
>> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
>> For additional commands, e-mail: dev-help at propel dot tigris dot org
>>
>>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
> For additional commands, e-mail: dev-help at propel dot tigris dot org
>

Re: [propel-dev] NestSet 1.3 branch merge

Reply

Author =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com>
Full name =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com>
Date 2007-10-27 19:42:26 PDT
Message Errr... why didn't you branch off my branch? Now things are gonna be
complicated.

Also, I don't get this whole sfPropelActAsNestedS​etBehaviourPlugin
stuff, care to explain?


David




Am 26.10.2007 um 14:06 schrieb Eric Fredj:

> I created a /heltem /branch to commit my Nestedset changes to avoid
> conflict on your branch if you planned some changes on it before merge
> in 1.3.
>
> That way, users can test my changes easily.
>
> I am currently working in sfPropelActAsNestedS​etBehaviourPlugin port
> to
> Propel core to support it natively.
>
> Regards,
> Heltem
>
> Eric Fredj a écrit :
>> Integrated PropelPDO in node runtime classes and builders too ;-)
>>
>> Eric Fredj a écrit :
>>
>>> David,
>>>
>>> I made a merge for 1.3 branch and yours on my dev host.
>>> I will submit it to you before commit it.
>>> I applied all david-multi_nested_set_tables changes and some of
>>> mine on 1.3.
>>>
>>> Moreover, I tried to follow API defined in
>>> sfPropelActAsNestedS​etBehaviorPlugin ...
>>>
>>> Waiting for your feedback. :-)
>>>
>>> Patch is attached.
>>>
>>> Regards,
>>> Heltem
>>>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
> For additional commands, e-mail: dev-help at propel dot tigris dot org
>
>

Re: [propel-dev] NestSet 1.3 branch merge

Reply

Author =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com>
Full name =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com>
Date 2007-10-27 19:40:11 PDT
Message For efficiency reasons, the system has converted the large body of this message into an attachment.
Attachments

Re: [propel-dev] NestSet 1.3 branch merge

Reply

Author Eric Fredj <eofredj at gmail dot com>
Full name Eric Fredj <eofredj at gmail dot com>
Date 2007-10-26 05:06:55 PDT
Message I created a /heltem /branch to commit my Nestedset changes to avoid
conflict on your branch if you planned some changes on it before merge
in 1.3.

That way, users can test my changes easily.

I am currently working in sfPropelActAsNestedS​etBehaviourPlugin port to
Propel core to support it natively.

Regards,
Heltem

Eric Fredj a écrit :
> Integrated PropelPDO in node runtime classes and builders too ;-)
>
> Eric Fredj a écrit :
>
>> David,
>>
>> I made a merge for 1.3 branch and yours on my dev host.
>> I will submit it to you before commit it.
>> I applied all david-multi_nested_set_tables changes and some of mine on 1.3.
>>
>> Moreover, I tried to follow API defined in
>> sfPropelActAsNestedS​etBehaviorPlugin ...
>>
>> Waiting for your feedback. :-)
>>
>> Patch is attached.
>>
>> Regards,
>> Heltem
>>

Re: [propel-dev] NestSet 1.3 branch merge

Reply

Author Eric Fredj <eofredj at gmail dot com>
Full name Eric Fredj <eofredj at gmail dot com>
Date 2007-10-25 18:46:37 PDT
Message Integrated PropelPDO in node runtime classes and builders too ;-)

Eric Fredj a écrit :
> David,
>
> I made a merge for 1.3 branch and yours on my dev host.
> I will submit it to you before commit it.
> I applied all david-multi_nested_set_tables changes and some of mine on 1.3.
>
> Moreover, I tried to follow API defined in
> sfPropelActAsNestedS​etBehaviorPlugin ...
>
> Waiting for your feedback. :-)
>
> Patch is attached.
>
> Regards,
> Heltem

[propel-dev] NestSet 1.3 branch merge

Reply

Author Eric Fredj <eofredj at gmail dot com>
Full name Eric Fredj <eofredj at gmail dot com>
Date 2007-10-25 18:41:29 PDT
Message David,

I made a merge for 1.3 branch and yours on my dev host.
I will submit it to you before commit it.
I applied all david-multi_nested_set_tables changes and some of mine on 1.3.

Moreover, I tried to follow API defined in
sfPropelActAsNestedS​etBehaviorPlugin ...

Waiting for your feedback. :-)

Patch is attached.

Regards,
Heltem

Re: [propel-dev] PHP5NestedSetPeerBuilder slightly broken (PATCH attached)

Reply

Author =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com>
Full name =?ISO-8859-1?Q?David_Z=FClke?= <dz at bitxtender dot com>
Date 2007-10-23 07:17:53 PDT
Message Sure, will do, even though it didn't really change in behavior I
think - AFAI I only fixed it in areas where it was broken before ;)



Am 23.10.2007 um 16:16 schrieb Hans Lellelid:

> Oh, ok. Sounds good.
>
> We do have some nested set documentation on the wiki. If the new
> classes change the way that stuff works, we should update it;
> otherwise,
> I think an email with the changes -- for those using the nested set
> stuff -- would be plenty.
>
> Hans
>
> David Zülke wrote:
>> 'twas just general nested set improvements and bug fixes :) yes, will
>> compile a mail describing the changes.
>>
>>
>> David
>>
>>
>>
>> Am 23.10.2007 um 16:10 schrieb Hans Lellelid:
>>
>>> I'm not sure what changes are in your branch exactly, so I'd just
>>> like
>>> to ask for some documentation for the new features / changes in
>>> behavior
>>> before we release.
>>>
>>> Merge at will, though! I'd like to get another beta out -- and
>>> an RC,
>>> eventually.
>>>
>>> Hans
>>>
>>> David Zülke wrote:
>>>> I'll see if that patch needs merging into my branch. Speaking of
>>>> which,
>>>> I'd like to merge it into the 1.3 branch ASAP. Objections, anyone?
>>>>
>>>>
>>>> David
>>>>
>>>>
>>>>
>>>>
>>>> Am 17.10.2007 um 11:25 schrieb Cameron Brunner:
>>>>
>>>>> Patch applied. Thank you very much for the bug report and patch!
>>>>>
>>>>> On 10/17/07, Felix Gilcher <propel at andersground dot net> wrote:
>>>>>> Hi,
>>>>>>
>>>>>> trying to add this as a ticket results in a 'Potential Spam'
>>>>>> error,
>>>>>> so I'm sending this to the list. I wonder what part matches the
>>>>>> filter ;)
>>>>>>
>>>>>> -----
>>>>>>
>>>>>> the generated BaseFooNestedSetPeer​::deleteNode() retrieves the
>>>>>> node
>>>>>> to delete and then calls delete() on it. However, it passes
>>>>>> (false,
>>>>>> $con) as parameter while Node::delete() only accepts $con and
>>>>>> thus,
>>>>>> the deletion fails.
>>>>>>
>>>>>> A patch to fix this issue is attached.
>>>>>> ------
>>>>>>
>>>>>> regards
>>>>>>
>>>>>> felix
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Cameron Brunner
>>>>>
>>>>> Want a better web browser?
>>>>> http://www.spreadfir​efox.com/?q=affiliat​es&id=182780​&t=1
>>>>>
>>>>> --------------------​--------------------​--------------------​------
>>>>> ---
>>>>> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
>>>>> For additional commands, e-mail: dev-help at propel dot tigris dot org
>>>>>
>>>>>
>>>>
>>>> --------------------​--------------------​--------------------​-------
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
>>>> For additional commands, e-mail: dev-help at propel dot tigris dot org
>>>>
>>>
>>> --------------------​--------------------​--------------------​--------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
>>> For additional commands, e-mail: dev-help at propel dot tigris dot org
>>>
>>>
>>
>> --------------------​--------------------​--------------------​---------
>> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
>> For additional commands, e-mail: dev-help at propel dot tigris dot org
>>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
> For additional commands, e-mail: dev-help at propel dot tigris dot org
>
>
Page: of 2 « Previous | Next »
Messages per page: