connected to the cvs2svn repository migration, I suggest to move
wxPython GUI code from grasssvn.fbk.eu to the OSGeo SVN repository
(before a final dumpstream will be prepared). I guess content of
'gui/wxpython' directory (strongly out-of-date) in CVS can be replaced
by the source code available in GRASS Add-Ons repository.
On Nov 17, 2007 9:55 AM, Martin Landa <landa.martin@gmail.com> wrote:
Hi all,
connected to the cvs2svn repository migration, I suggest to move
wxPython GUI code from grasssvn.fbk.eu to the OSGeo SVN repository
(before a final dumpstream will be prepared). I guess content of
'gui/wxpython' directory (strongly out-of-date) in CVS can be replaced
by the source code available in GRASS Add-Ons repository.
On 11/17/07 7:55 AM, "Martin Landa" <landa.martin@gmail.com> wrote:
Hi all,
connected to the cvs2svn repository migration, I suggest to move
wxPython GUI code from grasssvn.fbk.eu to the OSGeo SVN repository
(before a final dumpstream will be prepared). I guess content of
'gui/wxpython' directory (strongly out-of-date) in CVS can be replaced
by the source code available in GRASS Add-Ons repository.
Any objections?
Martin
__________________________________________
Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University
On Nov 17, 2007 9:55 AM, Martin Landa <landa.martin@gmail.com> wrote:
Hi all,
connected to the cvs2svn repository migration, I suggest to move
wxPython GUI code from grasssvn.fbk.eu to the OSGeo SVN repository
(before a final dumpstream will be prepared). I guess content of
'gui/wxpython' directory (strongly out-of-date) in CVS can be replaced
by the source code available in GRASS Add-Ons repository.
Any objections?
+1
+1, too. I just gave rsync access to Martin so that he can fetch and
convert the repository remotely.