Bug with morphic alignment

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug with morphic alignment

Mateusz Grotek
Reply | Threaded
Open this post in threaded view
|

Re: Bug with morphic alignment

laza
Hi Mateusz!

Thanks for taking the time to report the bug on the bug-tracker. In
doing so I guess you have some expectation, that someone will take
care of this. From my pov on Squeak this is most unlikely to happen,
if you don't take care of it yourself. If you find a fix to your
problem and upload it to the Inbox, there are chances that a bored
core developer will pick it up and uploads it to the trunk. [1]
Even if it doesn't make it into the trunk it might be the base for
another broader fix. Or it will help other people running into the
same problem, skimming through the Inbox to find a fix. Or it will
help you to build your own local repository of patches that you apply
to setup your working images based on Squeak trunk.

Alex

[1] http://squeakboard.wordpress.com/2009/07/02/a-new-community-development-model/

Reply | Threaded
Open this post in threaded view
|

Re: Bug with morphic alignment

Mateusz Grotek
Hi Alex,

 Or it will
> help you to build your own local repository of patches that you apply
> to setup your working images based on Squeak trunk.
>

How to apply a patch to a squeak image? Is there a tool for that? (I
don't want to change the whole method, but to apply a patch only if
possible)

Reply | Threaded
Open this post in threaded view
|

Re: Bug with morphic alignment

David T. Lewis
On Sat, Jan 14, 2012 at 07:19:18PM +0100, Mateusz Grotek wrote:

> Hi Alex,
>
>  Or it will
> > help you to build your own local repository of patches that you apply
> > to setup your working images based on Squeak trunk.
> >
>
> How to apply a patch to a squeak image? Is there a tool for that? (I
> don't want to change the whole method, but to apply a patch only if
> possible)

Usually people will use Montecello, so they make some changes and then
save them to the inbox repository for review. For the type of issue
that you reported, the fix is likely to be a small snippet of code,
so it would be perfectly fine to just make a small change set or a
fileout of the changed method and send it here to the list (and maybe
attach it to your Mantis report). In other words, if you have a proposed
fix and are not sure what to do with it, just do whatever is most
convenient for you, and refer to your Mantis bug report so people
will have the background :)

I'm glad that you entered the Mantis report. That keeps the issue
from getting lost, and even if it does not get fixed right away,
there is a pretty good chance that someone will address it eventually.

Dave


Reply | Threaded
Open this post in threaded view
|

Re: Bug with morphic alignment

Levente Uzonyi-2
On Sat, 14 Jan 2012, David T. Lewis wrote:

> On Sat, Jan 14, 2012 at 07:19:18PM +0100, Mateusz Grotek wrote:
>> Hi Alex,
>>
>>  Or it will
>>> help you to build your own local repository of patches that you apply
>>> to setup your working images based on Squeak trunk.
>>>
>>
>> How to apply a patch to a squeak image? Is there a tool for that? (I
>> don't want to change the whole method, but to apply a patch only if
>> possible)
>
> Usually people will use Montecello, so they make some changes and then
> save them to the inbox repository for review. For the type of issue
> that you reported, the fix is likely to be a small snippet of code,
> so it would be perfectly fine to just make a small change set or a
> fileout of the changed method and send it here to the list (and maybe
> attach it to your Mantis report). In other words, if you have a proposed
> fix and are not sure what to do with it, just do whatever is most
> convenient for you, and refer to your Mantis bug report so people
> will have the background :)

>From licensing and integration POV the use of Monticello and the Inbox is
preferred.


Levente

>
> I'm glad that you entered the Mantis report. That keeps the issue
> from getting lost, and even if it does not get fixed right away,
> there is a pretty good chance that someone will address it eventually.
>
> Dave
>
>
>