Hi Ken & friends,
somehow I wasn't aware that bugs can be categorized as Squeak packages/Seaside when I wrote this one
- http://bugs.squeak.org/view.php?id=5957
Would some good soul with admin privs please move it for me, TIA.
Cheers Klaus
Actually, any report you make is automatically going to be placed in your 'current' project, by default this is the Squeak project and that is the project which this bug is in. That looks perfectly fine to me. It is assigned to the category 'Kernel' and a glance at the discussion suggests that's probably accurate. If that is not the case then you are going to have to tell me to which package this issue relates.
Ken
On Mon, 2007-08-20 at 13:24 +0200, Klaus D. Witzel wrote:
Hi Ken & friends,
somehow I wasn't aware that bugs can be categorized as Squeak packages/Seaside when I wrote this one
Would some good soul with admin privs please move it for me, TIA.
Cheers Klaus
Oops, I missed the issue to 'Seaside' in there. OK, I'll move it, no problem.
Ken
On Mon, 2007-08-20 at 19:00 -0500, Ken Causey wrote:
Actually, any report you make is automatically going to be placed in your 'current' project, by default this is the Squeak project and that is the project which this bug is in. That looks perfectly fine to me. It is assigned to the category 'Kernel' and a glance at the discussion suggests that's probably accurate. If that is not the case then you are going to have to tell me to which package this issue relates.
Ken
On Mon, 2007-08-20 at 13:24 +0200, Klaus D. Witzel wrote:
Hi Ken & friends,
somehow I wasn't aware that bugs can be categorized as Squeak packages/Seaside when I wrote this one
Would some good soul with admin privs please move it for me, TIA.
Cheers Klaus
Hey, great, this I understand :)
Apparently my mail server today is very nervous with "on time", so I didn't receive this 2nd message together with you first ...
Thanks again Ken.
Cheers Klaus
On Tue, 21 Aug 2007 02:05:18 +0200, Ken Causey wrote:
Oops, I missed the issue to 'Seaside' in there. OK, I'll move it, no problem.
Ken
On Mon, 2007-08-20 at 19:00 -0500, Ken Causey wrote:
Actually, any report you make is automatically going to be placed in your 'current' project, by default this is the Squeak project and that is the project which this bug is in. That looks perfectly fine to me. It is assigned to the category 'Kernel' and a glance at the discussion suggests that's probably accurate. If that is not the case then you are going to have to tell me to which package this issue relates.
Ken
On Mon, 2007-08-20 at 13:24 +0200, Klaus D. Witzel wrote:
Hi Ken & friends,
somehow I wasn't aware that bugs can be categorized as Squeak packages/Seaside when I wrote this one
Would some good soul with admin privs please move it for me, TIA.
Cheers Klaus
Goog Morning Ken,
not that I understand one word of what you wrote, the report is no longer in Squeak's Kernel but, according to mantis, was explicitly moved by you to the place it belongs to (Seaside):
08-21-07 00:05 KenCausey Project Squeak => Squeak Packages 08-21-07 00:06 KenCausey Assigned To => renggli 08-21-07 00:06 KenCausey Status new => assigned 08-21-07 00:06 KenCausey Category Kernel => Seaside
Manne tak får inneting, as the nordish saying goes :)
Cheers Klaus
On Tue, 21 Aug 2007 02:00:57 +0200, you wrote:
Actually, any report you make is automatically going to be placed in your 'current' project, by default this is the Squeak project and that is the project which this bug is in. That looks perfectly fine to me. It is assigned to the category 'Kernel' and a glance at the discussion suggests that's probably accurate. If that is not the case then you are going to have to tell me to which package this issue relates.
Ken
On Mon, 2007-08-20 at 13:24 +0200, Klaus D. Witzel wrote:
Hi Ken & friends,
somehow I wasn't aware that bugs can be categorized as Squeak packages/Seaside when I wrote this one
Would some good soul with admin privs please move it for me, TIA.
Cheers Klaus
box-admins@lists.squeakfoundation.org