Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Warren Liu <warren@is...> - 2003-08-07 02:30:26
Just suggesting a little bit of file re-organization so that plog/ won't
have a huge number of files. Would it make sense or be possible to put
sectional files into their own directory?
ie. admin.* to admin/ so on and so forth?
And leave only the files that are used universally by all sections in
the main directory?
Haven't actually look at the code and how the entire system is organized
but just putting in this suggestion.
From: Oscar Renalias <oscar@re...> - 2003-08-07 07:56:58
That is something that it's been in my mind for some time now and it's
something that I'd like to do. However we will face two problems, sorted in
order of importance:
1) We will lose all the CVS history for the files if we move them, since CVS
does not support moving file accross the repository while keeping the
history. I am unsure wether the folks at sourceforge would be able to help us
2) I hate the way php handles "include"ing files without modifiying the
include_path directive in the php.ini file, specially when you are including
files which are in another folder which at the same time include some more
files that are in another different folder... I should either have a look at
how other php projects did that or simply include all the necessary files in
the entry points of pLog: admin.php and index.php (and also trackback.php,
register.php, summary.php and register.php)
I'll have a look at it and see what I can do.
On Thursday 07 August 2003 05:30, Warren Liu wrote:
> Hi all,
> Just suggesting a little bit of file re-organization so that plog/ won't
> have a huge number of files. Would it make sense or be possible to put
> sectional files into their own directory?
> ie. admin.* to admin/ so on and so forth?
> And leave only the files that are used universally by all sections in
> the main directory?
> Haven't actually look at the code and how the entire system is organized
> but just putting in this suggestion.
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> Plog-general mailing list