On Thu, Jun 06, 2002 at 05:58:42PM -0500, Jay Freeman (saurik) wrote:
> That's because most of these issues were _already_ flushed out in previous
And for people who are busy doing a lot of things, all the time, it is
*very* easy for posts to "get paged out". I certainly don't recall any
specific items, so a refresher will be needed.
Please consider this paragraph from the HACKING document, regarding patches
(which applies equally well to *any* post on this list):
If you don't get a response for a while, and don't see the patch
applied, it may just mean that people are really busy. Go ahead and
repost, and don't hesitate to point out that you're still waiting for
a response. One way to think of it is that patch management is highly
parallizable, and we need you to shoulder your share of the management
as well as the coding. Every patch needs someone to shepherd it
through the process, and the person best qualified to do that is the
I think Karl is basically asking for a refresher.
> I can rehash a lot of information, but I'm really not going to
> be bringing that much new to the table.
Absolutely, you will. We have no idea what you're referring to any more. At
a minimum, post links into the archives for review. But even better, write a
bulleted list with a sentence for each topic, and that link for more detail.
> The main one where I might have
> something new to say from the abbreviated list in my e-mail was the case
> sensitivity issue (which I can't remember a previous conversation about off
> the top of my head).
We have an open issue about that:
It hasn't been solved yet, and is really just waiting for somebody to work
on it. While we hope to have it solved for alpha, you can see in the issue
that I noted it might even slide to Beta simply because of the timing
> To note, the points about dsp files not being updated spawned from e-mails I
> noticed (while doing a search for "win32") from Patrik Husfloen. Take a
> look at "build error on win32" (which wasn't even replied to),
Maybe because it got fixed right away?
> and "rev 2062 does not build on win32" (which resulted in a few,
> semi-humourous comments from Brane, Greg, and yourself), both of which had
> to do with out-of-date dsp files.
Frankly, when I add a file, I forget to add it to the .dsp file. Simple as
that. And that behavior is particularly reinforced because I /don't/ have to
add the new file to anything on my dev platform. gen-make.py just happens to
find it and incorporate it for me.
I wrote some initial code for the .dsp generator, but I'm not sure that the
resulting .dsp files are Completely Right(tm), and I have no way to test
them. So that code is languishing until somebody on a Windows platform cares
to take the resulting .dsp files and try them out. And to tweak the
generator as appropriate.
Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Jun 6 03:23:41 2002