Re: imread on Octave 3.2.0 for Windows

[Alexander Mamonov]

Yes, I generated the diff from mercurial. I still have to learn how
the changesets are generated. When I do so, I'll submit a proper
changeset.

Regards,
Alex

On Wed, Jun 17, 2009 at 10:16 PM, John W. Eaton<address@hidden> wrote:
> On 17-Jun-2009, Alexander Mamonov wrote:
>
> | I encountered the problem with imread in 3.2.0 MinGW binary, and while
> | examining imread.m I noticed that it doesn't have any tests. So
> | following my own advice I'd like to suggest a patch. I couldn't test
> | it, since imread doesn't work with current 3.2.0 MinGW build, but it
> | runs OK with M*lab.
>
> Did you generate the diff from mercurial?  If so, how about submitting
> a changeset instead?  That way it is easier for us to apply and
> attribute the change to you.  Also, a simple ChangeLog entry should be
> included.  Something like
>
> 2009-06-17  Your Name  <address@hidden>
>
>        * image/imread.m: New test.
>
> in scripts/ChangeLog should do.
>
> Thanks,
>
> jwe
>