Re: [Patch] Encode invalid chars in /proc/registry entries (merge from 1.5)

2008-12-02 Thread Corinna Vinschen
On Dec 1 20:23, Christian Franke wrote: > This is a 1.5->1.7 merge of my patch from > http://sourceware.org/ml/cygwin-patches/2007-q4/msg00017.html > > Christian > > > 2008-12-01 Christian Franke <[EMAIL PROTECTED]> > > * fhandler_registry.cc (must_encode): New function. > (encode_r

[Patch] Encode invalid chars in /proc/registry entries (merge from 1.5)

2008-12-01 Thread Christian Franke
This is a 1.5->1.7 merge of my patch from http://sourceware.org/ml/cygwin-patches/2007-q4/msg00017.html Christian 2008-12-01 Christian Franke <[EMAIL PROTECTED]> * fhandler_registry.cc (must_encode): New function. (encode_regname): Ditto. (decode_regname): Ditto.

Re: [Patch] Encode invalid chars in /proc/registry entries

2007-11-22 Thread Corinna Vinschen
On Nov 16 20:25, Christian Franke wrote: > Corinna Vinschen wrote: >> Thanks for this patch. Apart from the missing ChangeLog I'm inclined >> to apply it to the upcoming 1.5.25 release, but I don't like to have it >> in HEAD as is. > > Thanks, I would appreciate to have this issue fixed in the bug

Re: [Patch] Encode invalid chars in /proc/registry entries

2007-11-16 Thread Christian Franke
Christopher Faylor wrote: On Fri, Nov 16, 2007 at 08:35:48PM +0100, Christian Franke wrote: Christopher Faylor wrote: .. Patch is tested with 1.5.24-2. Merge with HEAD looks good, but was not actually tested. Therefore, no changelog provided yet. Thanks for th

Re: [Patch] Encode invalid chars in /proc/registry entries

2007-11-16 Thread Christopher Faylor
On Fri, Nov 16, 2007 at 08:35:48PM +0100, Christian Franke wrote: > Christopher Faylor wrote: >> .. Patch is tested with 1.5.24-2. Merge with HEAD looks good, but was not actually tested. Therefore, no changelog provided yet. >>> Thanks for this patch. Apart from the missing

Re: [Patch] Encode invalid chars in /proc/registry entries

2007-11-16 Thread Christian Franke
Christopher Faylor wrote: .. Patch is tested with 1.5.24-2. Merge with HEAD looks good, but was not actually tested. Therefore, no changelog provided yet. Thanks for this patch. Apart from the missing ChangeLog I'm inclined to apply it to the upcoming 1.5.25 release, but I don't like to

Re: [Patch] Encode invalid chars in /proc/registry entries

2007-11-16 Thread Christian Franke
Hi Corinna, Corinna Vinschen wrote: ... Patch is tested with 1.5.24-2. Merge with HEAD looks good, but was not actually tested. Therefore, no changelog provided yet. Thanks for this patch. Apart from the missing ChangeLog I'm inclined to apply it to the upcoming 1.5.25 release, but I d

Re: [Patch] Encode invalid chars in /proc/registry entries

2007-11-16 Thread Christopher Faylor
On Fri, Nov 16, 2007 at 12:09:01PM +0100, Corinna Vinschen wrote: >Hi Christian, > >On Nov 15 22:56, Christian Franke wrote: >> Registry key and value names may contain chars which are not allowed within >> file names ('/', '\', ":"). But Cygwin's /proc/registry returns these names >> unchanged t

Re: [Patch] Encode invalid chars in /proc/registry entries

2007-11-16 Thread Corinna Vinschen
Hi Christian, On Nov 15 22:56, Christian Franke wrote: > Registry key and value names may contain chars which are not allowed within > file names ('/', '\', ":"). But Cygwin's /proc/registry returns these names > unchanged to the app. The obvious effect is that such entries cannot be > accessed

[Patch] Encode invalid chars in /proc/registry entries

2007-11-15 Thread Christian Franke
Registry key and value names may contain chars which are not allowed within file names ('/', '\', ":"). But Cygwin's /proc/registry returns these names unchanged to the app. The obvious effect is that such entries cannot be accessed. But if an entry name is identical to an existing path, more