Re: [heads up] Moving all blocks into /cocoon/blocks

2005-03-10 Thread Reinhard Poetz
Upayavira wrote: Reinhard Poetz wrote: Reinhard Poetz wrote: I plan to move all blocks from /cocoon/trunk/src/blocks into /cocoon/blocks/[status]/name/trunk the same way as I did it with cron, authentication-fw, session-fw and html. As nobody complained, I think that there haven't been any

Re: [heads up] Moving all blocks into /cocoon/blocks

2005-03-10 Thread Daniel Fagerstrom
Reinhard Poetz wrote: snip/ So far, I've moved all blocks from /trunk/src/blocks to /blocks/[status]/[name]/trunk and updated the svn:external property on /trunk/src/blocks to re-import them at their former place. This way everything should work as it did before the change. Cool! As I

Re: [heads up] Moving all blocks into /cocoon/blocks

2005-03-09 Thread Reinhard Poetz
Reinhard Poetz wrote: I plan to move all blocks from /cocoon/trunk/src/blocks into /cocoon/blocks/[status]/name/trunk the same way as I did it with cron, authentication-fw, session-fw and html. As nobody complained, I think that there haven't been any problems. If you want to avoid problems

Re: [heads up] Moving all blocks into /cocoon/blocks

2005-03-09 Thread Upayavira
Reinhard Poetz wrote: Reinhard Poetz wrote: I plan to move all blocks from /cocoon/trunk/src/blocks into /cocoon/blocks/[status]/name/trunk the same way as I did it with cron, authentication-fw, session-fw and html. As nobody complained, I think that there haven't been any problems. If you

[heads up] Moving all blocks into /cocoon/blocks

2005-03-04 Thread Reinhard Poetz
I plan to move all blocks from /cocoon/trunk/src/blocks into /cocoon/blocks/[status]/name/trunk the same way as I did it with cron, authentication-fw, session-fw and html. As nobody complained, I think that there haven't been any problems. If you want to avoid problems with pending changes