On Fri, 28 Jan 2000 01:38:32 +0100, Marc Lehmann [EMAIL PROTECTED] said:
Ok. I've just enabled automatic mirroring from the sourceforge cvs
back to the gimp cvs.
FWIW, I think this should be used sparingly. It is my belief that
we should try to move plugins into a separate package from the
Hi,
Ok. I've just enabled automatic mirroring from the sourceforge cvs back
to the gimp cvs.
The file gimp/PLUGIN_CVS in the cvs tree controls which paths are mirrored
and which are not. If anything goes havoc just delete that file and the
script will stop doing anything.
At the
Hi,
Ok. I've just enabled automatic mirroring from the sourceforge cvs back
to the gimp cvs.
The file gimp/PLUGIN_CVS in the cvs tree controls which paths are mirrored
and which are not. If anything goes havoc just delete that file and the
script will stop doing anything.
At the
Ok. I've just enabled automatic mirroring from the sourceforge cvs back
to the gimp cvs.
The file gimp/PLUGIN_CVS in the cvs tree controls which paths are mirrored
and which are not. If anything goes havoc just delete that file and the
script will stop doing anything.
At the moment, only
On Fri, Jan 28, 2000 at 01:38:32AM +0100, Marc Lehmann wrote:
plug-ins/maze/*
is being written back. This (unfortunately!!) means that changes done to
these files in the gimp cvs will get overwritten. I've not found a better
way to synchronize two cvs trees better (maybe CVSup would
