Hi Maciek,
2007/12/11, Maciej Sieczka <[EMAIL PROTECTED]>:
> Interesting. Is this export feature documented somwhere? How
> did you find it out?
http://lists.edgewall.com/archive/trac/2006-April/007535.html
Martin
--
Martin Landa <[EMAIL PROTECTED]> * http://gama.fsv.cvut.cz/~landa *
Martin Landa wrote:
> this URL should generate XML file with tickets definition of the given
> group (atid=188) (which can be used as an input for
> sourceforge2trac.py script)
>
> http://wald.intevation.org/export/tracker.php?atid=188&group_id=21
>
> but it is generating invalid, almost empty f
Hi,
2007/12/10, Maciej Sieczka <[EMAIL PROTECTED]>:
> Martin Landa wrote:
>
> > But the export from GForge failed
>
> How did you do this "export"?
this URL should generate XML file with tickets definition of the given
group (atid=188) (which can be used as an input for
sourceforge2trac.py script
Martin Landa wrote:
> But the export from GForge failed
How did you do this "export"?
If all goes well we'll get an SQL dump of GRASS GForge
trackers content from Sascha. Would it be easy to import
this into Trac?
Maciek
___
grass-user mailing list
gr
Hi Maciek,
2007/12/10, Maciej Sieczka <[EMAIL PROTECTED]>:
> Markus Neteler wrote:
>
> > # Tickets (have to be migrated from GForge and maybe also RT)
> > http://trac.osgeo.org/grass/report
>
> Working on it [1]. Propably can do for GForge; propably
> won't-do for RT - too much mess there; I'd lea
Markus Neteler wrote:
> # Tickets (have to be migrated from GForge and maybe also RT)
> http://trac.osgeo.org/grass/report
Working on it [1]. Propably can do for GForge; propably
won't-do for RT - too much mess there; I'd leave as it is.
I'm still keeping an eye on RT, closing tickets for issues
