Re: [ccache] Release plan

Joel Rosdahl wrote: Hi, I now don't have any features left on my TODO list for the next ccache release, which I plan to name 3.0. The main thing left, except more testing and fixing any bugs that are found, is some work on the documentation, and maybe some portability stuff. There are still

[ccache] ccache 3.0pre0 has been released

Hi, I'm pleased to announce ccache version 3.0pre0. I expect this prerelease (or call it beta release if you want) to not differ much from the upcoming 3.0 release functionality-wise, so I encourage everyone to try it out. And please report any bugs or misbehaviours you find to this mailing list o

Re: [ccache] Release plan

On Sun, Feb 28, 2010 at 5:11 PM, Joel Rosdahl wrote: > And does anyone have other feature requests or > semi-forks with features that could be incorporated in later ccache versions? I have a win32 port almost done. But since it touches *a lot* of code I'd rather wait for after 3.0 so it can recei

[ccache] Release plan

Hi, I now don't have any features left on my TODO list for the next ccache release, which I plan to name 3.0. The main thing left, except more testing and fixing any bugs that are found, is some work on the documentation, and maybe some portability stuff. There are still some features that I woul

Re: [ccache] [PATCH] Always close(fd) as soon as file is mmap()'d.

On Sun, 28 Feb 2010 12:22:56 -0300 Ramiro Polla wrote: > On Sun, Feb 28, 2010 at 5:52 AM, Joel Rosdahl wrote: > > On Sat, 27 Feb 2010 22:15:54 -0300 > > Ramiro Polla wrote: > >> On remember_include_file(), close() wasn't even being called. On > >> unify_hash() and process_preprocessed_file(), i

Re: [ccache] [PATCH] Always close(fd) as soon as file is mmap()'d.

On Sat, 27 Feb 2010 22:15:54 -0300 Ramiro Polla wrote: > On remember_include_file(), close() wasn't even being called. On > unify_hash() and process_preprocessed_file(), it might not be closed > if mmap fails. Thanks for finding this! But I think you forgot to attach your patch? -- Joel ___