Re: [Gimp-developer] sourceforge cvs issue

2003-02-09 Thread Tor Lillqvist
Sven Neumann writes: > IMO Tor should commit his filename-conversion hacks. I wrote: > OK, I'll merge them in then, with ifdefs as appropriate not to affect > behaviour on Unix. I'll probably have time to do it next weekend. It took some time before I could do it, but now I have merged in tho

Re: [Gimp-developer] sourceforge cvs issue

2003-01-29 Thread Sven Neumann
Hi, Raphaël Quinet <[EMAIL PROTECTED]> writes: > Hmmm... Sure, this is not very clean. On the other hand, there are a > couple of quick workarounds that have been introduced in the 1.2.x > branch while the proper solutions have only been implemented in the > 1.3.x branch. IIRC, there is at lea

Re: [Gimp-developer] sourceforge cvs issue

2003-01-28 Thread Patrick McFarland
Tor, sf.net wont remove the wingimp project until you, or any other qualified gimp developer tells them to. The project is already breaking atleast one rule, the one about only developers for a project can start a sf.net project about the said project. Please take care of this before it gets out o

Re: [Gimp-developer] sourceforge cvs issue

2003-01-28 Thread Raphaël Quinet
On Tue, 28 Jan 2003 16:38:28 +, Tor Lillqvist <[EMAIL PROTECTED]> wrote: > Raphaël Quinet writes: > > From my point of view, I think that it would be better to integrate > > these changes before the 1.2.4 release. > > It's just that maybe half of the changes are really quite ugly hacks > t

Re: [Gimp-developer] sourceforge cvs issue

2003-01-28 Thread Tor Lillqvist
Raphaël Quinet writes: > From my point of view, I think that it would be better to integrate > these changes before the 1.2.4 release. It's just that maybe half of the changes are really quite ugly hacks to get non-ASCII file and directory names working somewhat better on Windows, where GTK+ 1

Re: [Gimp-developer] sourceforge cvs issue

2003-01-28 Thread Raphaël Quinet
On Tue, 28 Jan 2003 01:15:07 +, Tor Lillqvist <[EMAIL PROTECTED]> wrote: > Branko Collin writes: > > Is not all your code in the GIMP CVS repository? If so, why not? > > I have told this several times, most recently earlier today: > > I have local changes I haven't committed to the (real)

Re: [Gimp-developer] sourceforge cvs issue

2003-01-27 Thread Branko Collin
On 28 Jan 2003, at 1:15, Tor Lillqvist wrote: > Branko Collin writes: > > Is not all your code in the GIMP CVS repository? If so, why not? > > I have told this several times, most recently earlier today: > > I have local changes I haven't committed to the (real) GIMP CVS, > true. [...] As s

Re: [Gimp-developer] sourceforge cvs issue

2003-01-27 Thread Tor Lillqvist
Branko Collin writes: > Is not all your code in the GIMP CVS repository? If so, why not? I have told this several times, most recently earlier today: I have local changes I haven't committed to the (real) GIMP CVS, true. [...] As soon as 1.2.4 has been officially released I'll try to see h

Re: [Gimp-developer] sourceforge cvs issue

2003-01-27 Thread Branko Collin
On 27 Jan 2003, at 18:54, Tor Lillqvist wrote: > Mat Caughron writes: > > NOT to fork the project but to make it more available. It seems > the only > way to see the current windows-gimp 1.2.4 source is to > download the zip > file from: > www.gimp.org/win32/downloads-20030104.html > Even if

[Gimp-developer] sourceforge cvs issue

2003-01-27 Thread Tor Lillqvist
Mat Caughron writes: > NOT to fork the project but to make it more available. It seems the only > way to see the current windows-gimp 1.2.4 source is to download the zip > file from: www.gimp.org/win32/downloads-20030104.html > Even if you want to look up a particular file, you have to downloa