Re: Connection problems with Greek mirror fosszone.csd.auth.gr

sucked me in and there's no way out, it seems. I plan to return and will return (hopefully soon) as your assistant. > On Thu, Feb 13, 2025 at 10:13:32PM +0200, Yavor Doganov wrote: > > I'm having constant problems with the Greek mirror > > fosszone.csd.auth.gr > I can&

Connection problems with Greek mirror fosszone.csd.auth.gr

Hi Savannah hackers, First of all, thanks for your tireless work. I'm having constant problems with the Greek mirror fosszone.csd.auth.gr (I live in Bulgaria and apparently the GeoIP magic decides that's the one to use, although there are other mirrors even over the Atlantic Ocean which have bett

Re: Non-ASCII subjects garbled in thread view of the mail archives

Svetlana Tkachenko wrote: > Yavor Doganov написал(а): > > How do you know it is the latest version? > > The version is written in the first line in the page HTML source. Ah, right. It says v2.6.19+ while the one on the Debian list is v2.6.19 (without the plus). So perhaps there

Re: Non-ASCII subjects garbled in thread view of the mail archives

Svetlana Tkachenko wrote: > The page you linked was generated using the latest version of > https://www.mhonarc.org/ . How do you know it is the latest version? IME, GNU servers seldom run latest versions of anything. > Yet, another page using the same software > https://lists.debian.org/debian

Re: Non-ASCII subjects garbled in thread view of the mail archives

Svetlana Tkachenko wrote: > There is no encoding specified at this page. I think adding charset="utf-8" /> would resolve this. Yes, I guess it's something trivial as that. But the Subject: header may be in a different encoding; that's perfectly valid. The software that is generating the web pag

Non-ASCII subjects garbled in thread view of the mail archives

[ Perhaps sysad...@gnu.org is the right place to report this -- if so, please bounce/forward the message and sorry for bothering. ] I have a vague feeling that I've reported this before, some (many?) years ago. A Subject: of an email message in UTF-8 encoding but containing other than US-ASCII

[Savannah-help-public] Re: CVS server access at savannah

Evgeniy Sudyr wrote: > How can I update or even delete news published there You can't. Retroactive editing or deletion of news items was never considered a feature worth implementing, AFAIK. It's like a VCS or a mailing list: consider committing again undoing the damage done in the previous comm

[Savannah-help-public] Re: CVS server access at savannah

Evgeniy Sudyr wrote: > I noticed that at CVS pages disappeared for our team project at > Savannah - https://savannah.gnu.org/projects/www-uk/ It looks like it's deactivated from Main -> Select Features. > Can you suggest how to deal with version control for our > translations project? That's up

[Savannah-help-public] [sr #107473] CVS permission denied - www-ro translation

Update of sr #107473 (project administration): Status:None => Invalid Assigned to:None => yavor Open/Closed:Open => Closed __

[Savannah-help-public] [sr #106712] accepting follow-ups by email

Follow-up Comment #17, sr #106712 (project administration): Forgot to add: My personal impression is that dropping the Savane trackers should be completely out of the question, and it was never considered, IIRC. Sylvain can tell for sure. Some projects (e.g. GNUstep) actually like them. Implem

[Savannah-help-public] [sr #106712] accepting follow-ups by email

Follow-up Comment #16, sr #106712 (project administration): There is an official debbugs instance (debbugs.gnu.org); all GNU projects are welcome to use it, TTBOMK. It has nothing to do with Savannah, though, and there's no integration at all. ___

[Savannah-help-public] [sr #107431] mail-to-bugs gateway

Follow-up Comment #7, sr #107431 (project administration): It's already reported -- see sr #106712. ___ Reply to this item at: ___ Message sent via

[Savannah-help-public] [sr #107359] GNU Bazaar not listed among supported VCS

Follow-up Comment #2, sr #107359 (project administration): AFAIK Bzr support is still unofficial/experimental, so perhaps it might not be a good idea to advertize it (yet). It doesn't sound like an advertisement anyway, given the current experience :-). _

[Savannah-help-public] [gnu.org #391056] Re: [Fwd: Mail delivery failed: returning message to sender]

Hossam Hossny wrote: > This looks like something to drive savannah-hackers attention to Actually no, the sysadmins are the ones who can fix this. Some time ago, they added a size restriction in order to reduce excessive bandwith resulting from large messages occasionally sent to the lists. This

[Savannah-help-public] [sr #107201] No luck on ssh

Follow-up Comment #5, sr #107201 (project administration): You have to be a member of at least one project if you want to use the :ext method. ___ Reply to this item at: ___

[Savannah-help-public] [sr #107183] GRUB web pages

Follow-up Comment #2, sr #107183 (project administration): I feel a bit guilty as I advised Robert to ask the Savannah hackers for this, although I knew in advance what the reply would be. At least he deserves some explanation why things are what they are. I'll try to describe that from my POV.

[Savannah-help-public] [sr #107148] Request to enable mail delivery on cvs commit hook

Update of sr #107148 (project administration): Status:None => Done Assigned to:None => yavor Open/Closed:Open => Closed __

[Savannah-help-public] [sr #107147] Request to enable mail delivery on cvs commit hook

Update of sr #107147 (project administration): Status:None => Done Assigned to:None => yavor Open/Closed:Open => Closed __

Re: [Savannah-help-public] missing SSL cert from savannah site

Richard Stallman wrote: > I know nothing about this; I might not know how to do it. > I hope you are not saying that people like me are unimportant > when we judge what Savannah should do. No, not at all. It's perfectly OK not to know or bother (but we provide simple instructions for those who ca

Re: [Savannah-help-public] missing SSL cert from savannah site

Matt Lee wrote: > Until this situation changes, we should continue with the practice > of buying certificates like do for www.fsf.org IOW, you suggest to continue feeding the monster and actively discourage community-driven CAs.

Re: [Savannah-help-public] missing SSL cert from savannah site

Matt Lee wrote: > I don't think this is about clueless users, and I find it pretty sad > that we're talking about people like that. OK, I withdraw my words. What this is all about, really? > Free software is for everyone, and used by people who may seem > clueless about this problem, but it's be

Re: [Savannah-help-public] missing SSL cert from savannah site

Sylvain Beucler wrote: > Mozilla follows money-based audit. Right, and because of this, they decided to make certificate errors in xulrunner 1.9 fatal (i.e. Firefox 3.x). The user has to jump through hoops to make the browser believe the certificate is valid, thus finally allowing access to the s

[Savannah-help-public] [sr #107044] Using SVN instead of CVS for website

Update of sr #107044 (project administration): Status:None => Wont Do Open/Closed:Open => Closed ___ Follow-up Comment #2: Yes, unfort

[Savannah-help-public] [sr #106531] Bazaar commit notification emails omit large diffs

Follow-up Comment #15, sr #106531 (project administration): There is no limit for the diff size for CVS repositories, so I don't see why there should be for Bzr. Restrictions for the size should be implemented further in the chain -- MTA, mailing list setup, etc. For Emacs specifically, it has

[Savannah-help-public] [sr #106531] Bazaar commit notification emails omit large diffs

Follow-up Comment #13, sr #106531 (project administration): IMVHO this is the wrong place to put any limitations wrt size. ___ Reply to this item at: ___

[Savannah-help-public] [sr #106999] Can't import project module to savannah

Update of sr #106999 (project administration): Status:None => Invalid Assigned to:None => yavor Open/Closed:Open => Closed __

[Savannah-help-public] [sr #106983] Forward CVS changes in emacs/lisp/org/* to an email address

Update of sr #106983 (project administration): Status:Done => Need Info Open/Closed: Closed => Open ___ Follow-up Comment #3: We can only

[Savannah-help-public] [sr #106983] Forward CVS changes in emacs/lisp/org/* to an email address

Update of sr #106983 (project administration): Status: Need Info => Done Open/Closed:Open => Closed ___ Follow-up Comment #5: Carsten wro

[Savannah-help-public] [sr #106983] Forward CVS changes in emacs/lisp/org/* to an email address

Update of sr #106983 (project administration): Status:None => Done Assigned to:None => yavor Open/Closed:Open => Closed __

Re: [Savannah-help-public] avr-libc repo missing

Weddington, Eric wrote: > Any idea what's going on? This should be fixed now. See https://savannah.gnu.org/support/?106955 if you are curious about the details.

[Savannah-help-public] [sr #106955] trans-coord CVS repository missing

URL: Summary: trans-coord CVS repository missing Project: Savannah Administration Submitted by: yavor Submitted on: Sat 01 Aug 2009 06:55:36 PM EEST Category: Developer CVS

Re: [Savannah-help-public] impossible connection to cvs repository

Malo Pichot wrote: > Sylvain Beucler a écrit : > > Check the homepage :) > > Heu... OK ! :-) I did not received the information email. Probably because you are not subscribed to savannah-announce or savannah-users? Unlike other hosting sites, Savannah does not bombard all users with bulk email :

[Savannah-help-public] [sr #106712] accepting follow-ups by email

Follow-up Comment #4, sr #106712 (project administration): On second thought, why there is a need for authentication at all? As it stands now, anonymous users can open bugs/tasks and can follow-up. The "only" thing that needs to be done is to craft all mail from the trackers to have a Reply-To:

[Savannah-help-public] [sr #106712] accepting follow-ups by email

Follow-up Comment #3, sr #106712 (project administration): I second this wishlist request -- the web-based trackers is something I dislike in Savannah. I have the feeling that the implementation would be far from trivial. FTR, debbugs has no authentication. Everyone can send messages and can m

[Savannah-help-public] [sr #106701] CVS commit notification partially broken

Update of sr #106701 (project administration): Status: Ready For Test => Done Open/Closed:Open => Closed ___ Follow-up Comment #3: Yes, appear

[Savannah-help-public] CVS commit notifications not working reliably

I noticed that since a few days ago, commit notifications are not always delivered, and the following message is being printed in such cases: Triggering webpages update... Insecure dependency in sprintf while running with -T switch at /usr/local/bin/log_accum.pl line 816. Could it be related to t

[Savannah-help-public] Re: [gnu.org #409520] Translation in russian

[ CCing sv-hackers -- the question is about translating Savannah. ] Koptev Oleg via RT wrote: > Sorry, but their maillist seems to be dead, judging by archive. If you have questions, please write to that list. It is mostly for announcements of string freezes, IIRC. A few months with little or n

[Savannah-help-public] [sr #106619] The new mirror framework breaks uscan

Update of sr #106619 (project administration): Status:None => Invalid Open/Closed:Open => Closed ___ Follow-up Comment #2: Gar, it's a

[Savannah-help-public] [sr #106619] The new mirror framework breaks uscan

URL: Summary: The new mirror framework breaks uscan Project: Savannah Administration Submitted by: yavor Submitted on: Wed Jan 28 16:20:47 2009 Category: Project download area (no

[Savannah-help-public] [sr #106531] Bazaar commit notification emails omit large diffs

Follow-up Comment #8, sr #106531 (project administration): > almost no one wants to receive those The problem is that "almost no one" != "absolutely no one". AFAIK commit notifications is the only way some people (rms for example) track development, and others simply hate anything web-related.

[Savannah-help-public] [sr #106585] GUG revision control system other than CVS

Update of sr #106585 (project administration): Status:None => Invalid Assigned to:None => yavor Open/Closed:Open => Closed __

[Savannah-help-public] [sr #106575] Website replication for trans-coord not working

URL: Summary: Website replication for trans-coord not working Project: Savannah Administration Submitted by: yavor Submitted on: Sun 07 Dec 2008 05:37:50 PM EET Category: Project

[Savannah-help-public] [sr #106478] After committed to www project's (www.gnu.org) webpages repo, a commit message won't be sent on www-commits mailing list

Follow-up Comment #44, sr #106478 (project administration): > Did you rather mean "the absence of fix"? No, I meant that the changes you made to "fix" Ali's problem had the negative effect of losing commit notifications (even in the form of a bounce to the committer), which is now hopefully not

[Savannah-help-public] [sr #106478] After committed to www project's (www.gnu.org) webpages repo, a commit message won't be sent on www-commits mailing list

Update of sr #106478 (project administration): Status:None => Done Open/Closed:Open => Closed ___ Follow-up Comment #42: Closing th

[Savannah-help-public] Re: [gnu.org #391056] Re: Reviewing changes

.org ([199.232.41.69]) by sv.gnu.org with esmtp (Exim 4.63) (envelope-from <[EMAIL PROTECTED]>) id 1L66Ku-0003n1-6b for [EMAIL PROTECTED]; Fri, 28 Nov 2008 16:36:56 + Received: from yavor by cvs.savannah.gnu.org with local (Exim 4.63) (envelope-from <

[Savannah-help-public] [sr #106561] gpicker submission cancellation request

Update of sr #106561 (project administration): Status:None => Wont Do Open/Closed:Open => Closed ___ Follow-up Comment #3: I have appr

[Savannah-help-public] [sr #106561] gpicker submission cancellation request

Update of sr #106561 (project administration): Assigned to:None => yavor ___ Follow-up Comment #1: I reviewed your package and it looks fine. I could approve the project now, if you wish

Re: [Savannah-help-public] Re: [Savannah-hackers-public] Re: Reviewing changes

Sylvain Beucler wrote: > > I'm not sure we have to change anything on the Savannah side though. I've made the change for the emacs project, so nothing in that regard is needed. > Currently I think a multi-files commit will send 2 mails, one with > all the diffs to emacs-diffs and one with the co

[Savannah-help-public] Re: [Savannah-hackers-public] Re: Reviewing changes

Sylvain Beucler wrote: > > Is it possible to clarify this request? Until a few months ago, the Emacs commit policy was to commit every file separately, with the commit message specific for the change of that file, and afterwards to commit the ChangeLog with no commit message. AFAIU, this was in

Re: [Savannah-help-public] CVS versus SVN

David Hill wrote: > > I understand that projects can use Subversion (SVN) instead of CVS Projects can use whatever VCS supported by Savannah they wish (which currently means CVS, Subversion, GNU Arch, Git and Mercurial -- GNU Bzr is in testing phase and not yet officially supported). > direct

Re: [Savannah-help-public] [sr #106531] Bazaar commit notification emails omit large diffs

Karl Berry wrote: > > I still see and approve messages over 100k. Interesting, I do not receive such messages for approval for my lists. Or maybe it's a listhelper thing? > Also, I'm not sure if the limit is really only on attachments; From my experience it is not only on attachments. > since

[Savannah-help-public] [sr #106478] After committed to www project's (www.gnu.org) webpages repo, a commit message won't be sent on www-commits mailing list

Follow-up Comment #40, sr #106478 (project administration): > It is highly undesirable for me to change this piece Yeah, I can imagine and suspected so. Agreed completely. > Which reminds me somebody offered Perl skills recently Certainly not me, Perl looks like output from /dev/random to me.

[Savannah-help-public] [sr #106478] After committed to www project's (www.gnu.org) webpages repo, a commit message won't be sent on www-commits mailing list

Follow-up Comment #38, sr #106478 (project administration): >> If the message is rejected due to (say) size limit, the user >> won't get a bounce. This happened several times already. > In this case, what we need is patching CVS log_accum to support > diff size limit You mean, if the message

[Savannah-help-public] [sr #106478] After committed to www project's (www.gnu.org) webpages repo, a commit message won't be sent on www-commits mailing list

Follow-up Comment #36, sr #106478 (project administration): Hmm, I'm not sure, but I think this implementation will have nefarious effects sometimes. If the message is rejected due to (say) size limit, the user won't get a bounce. This is important for me, because GNUN builds often generate lar

[Savannah-help-public] [sr #106478] After committed to www project's (www.gnu.org) webpages repo, a commit message won't be sent on www-commits mailing list

Follow-up Comment #28, sr #106478 (project administration): I couldn't understand whether they acknowledge the problem but are unable to fix it or they claim that it is gnu.org's fault? This is definitely a problem of your service -- please tell them to try the session with mx.pittle.org at comm

[Savannah-help-public] [sr #106485] Character encoding

Follow-up Comment #1, sr #106485 (project administration): This is a known issue, see the explanation by Justin Baugh (one of the FSF sysadmins) at . Maybe it's time to raise it again. For the time being I'd recommend dow

[Savannah-help-public] [sr #106478] After committed to www project's (www.gnu.org) webpages repo, a commit message won't be sent on www-commits mailing list

Follow-up Comment #26, sr #106478 (project administration): I think I am beginning to realize why you can post directly but notifications are not delivered. When you post to a GNU mailing list (or to me personally, it doesn't matter), the message is picked by fw-pool-128.gruppocredit.it (your IS

[Savannah-help-public] [sr #106478] After committed to www project's (www.gnu.org) webpages repo, a commit message won't be sent on www-commits mailing list

Follow-up Comment #25, sr #106478 (project administration): Your mail server rejects bounces, i.e. it cannot handle mail from the null envelope sender address. Look how there is no problem here: $ telnet mx.pittle.org 25 Trying 65.254.254.50... Connected to mx.pittle.org. Escape character is '^

[Savannah-help-public] [sr #106478] After committed to www project's (www.gnu.org) webpages repo, a commit message won't be sent on www-commits mailing list

Follow-up Comment #23, sr #106478 (project administration): First -- no need to send anything to sysadmin, Sylvain already did that yesterday with CC to you. Second -- the link Sylvain gave in comment #17 is pretty descriptive. Before accepting the message, lists.gnu.org does this SMTP callback

[Savannah-help-public] [sr #106478] After committed to www project's (www.gnu.org) webpages repo, a commit message won't be sent on www-commits mailing list

Follow-up Comment #21, sr #106478 (project administration): No clues; perhaps this SMTP callback is performed only under certain conditions -- for example, for messages coming from cvs.savannah.gnu.org. The sysadmins will tell. Meanwhile, this is a legitimate way to perform sender verification.

[Savannah-help-public] [sr #106478] After committed to www project's (www.gnu.org) webpages repo, a commit message won't be sent on www-commits mailing list

Follow-up Comment #14, sr #106478 (project administration): It might be a temporary problem as Sylvain says (although I doubt it, as I advised you to open a support request if the problem persists). Try to commit these days, and if it's not delivered to the list, write to [EMAIL PROTECTED] (and

[Savannah-help-public] [sr #106478] After committed to www project's (www.gnu.org) webpages repo, a commit message won't be sent on www-commits mailing list

Follow-up Comment #9, sr #106478 (project administration): I find it odd that he posts without problem to GNU mailing lists directly, for example:

[Savannah-help-public] [sr #106481] Not sure if www-tr-admin ML is created successfully

Follow-up Comment #2, sr #106481 (project administration): TTBOMK, archives won't be created until the first message is sent. Have you done this already? ___ Reply to this item at: ___

[Savannah-help-public] [sr #106478] After committed to www project's (www.gnu.org) webpages repo, a commit message won't be sent on www-commits mailing list

Follow-up Comment #7, sr #106478 (project administration): Most probably this is due to DNS mismatch: $ dig -t MX pittle.org mx.pittle.org. 1592IN A 65.254.254.52 mx.pittle.org. 1592IN A 65.254.254.50 mx.pittle.org. 1592IN A

[Savannah-help-public] [sr #106478] After committed to www project's (www.gnu.org) webpages repo, a commit message won't be sent on www-commits mailing list

Follow-up Comment #4, sr #106478 (project administration): He is committing to the web repository of the "www" project like any other webmaster, so there should be notification to www-commits for all check-ins. Of course translation projects are different projects and should have nothing to do w

[Savannah-help-public] [sr #106478] After committed to www project's (www.gnu.org) webpages repo, a commit message won't be sent on www-commits mailing list

Follow-up Comment #2, sr #106478 (project administration): This is news to me, and I think there's some misunderstanding. Ali was complaining previously to trans-coord-discuss that his commits do not end up as notifications. I can only confirm that, and this is no default; it's undesirable beha

[Savannah-help-public] [sr #106473] Project submission backlog

Follow-up Comment #2, sr #106473 (project administration): We are well aware about the backlog, and nobody would deny it's a serious problem. Currently we are discussing a new process which would enable us to avoid this situation in the future. However, please understand that project reviews, a

Re: [Savannah-help-public] Re: Fw: CVS for webpages not mirroring?

Ben Pfaff wrote: > > > Apparently there was a index.html->pspp.html obsolete entry in > > '.symlinks'. I removed it. > > Wow, I look silly now. No, you don't: .symlinks files are something very obscure and just a dirty workaround for CVS' inability to deal with real symlinks. It is entirely nat

Re: [Savannah-help-public] Re: Redirecting bug-gnu-emacs to emacsbugs

Stefan Monnier wrote: > > Yes, the intention is to move the Debbugs to a gnu.org machine once > we're satisfied with the way it works, Is it going to be solely dedicated to Emacs (with Emacs components set as "packages" in debbugs' context), or something more global, like every Savannah project h

Re: [Savannah-help-public] Helping in Savannah

Franco, I am very happy that you volunteer for the tedious field of Savannah projects approval (where help is always needed) and I don't want to pull the blanket to my side, but... I hope that this new responsibility of yours doesn't decrease drastically the time you spend on the Spanish gnu.org t

[Savannah-help-public] [gnu.org #357472] Regarding nonGNU mirror at my server

Does anyone have a clue what might be the problem? [received at webmasters] Requestors: neverstable @ gmail.com This is Pratyush , i am a Savannah user,(username: pratyush). I would like to mirror the nongnu releases from Savannah, but when i followed the steps shown at http://www.gnu.org/ser

[Savannah-help-public] [sr #105528] Deal with encoding issues in log_accum

Follow-up Comment #13, sr #105528 (project administration): I took a look at the log_accum and svnmailer, and I agree that it is not trivial at all to implement auto-guessing of the encoding; also this approach is almost certainly doomed to fail (for example, the log message in ISO-8859-15, one f

[Savannah-help-public] [sr #105528] Deal with encoding issues in log_accum

Follow-up Comment #11, sr #105528 (project administration): "I doubt it, because I don't think there's a magic solution to this issue..." Maybe -- I don't argue at all, but I read all those mails with Mutt (takes about ~15 minutes to load on my mailbox). Basically, I only experienced this issue

[Savannah-help-public] [sr #105528] Deal with encoding issues in log_accum

Follow-up Comment #9, sr #105528 (project administration): Sylvain, I think that you can safely ignore this issue. I checked two other projects (non-Savannah) and it looks like none of them is adding a `Content-Type' header. It seems that svnmailer (and other modern VCS tools) have logic to aut

[Savannah-help-public] [sr #106227] Commit messages for "trans-coord"

URL: Summary: Commit messages for "trans-coord" Project: Savannah Administration Submitted by: yavor Submitted on: Saturday 01/12/08 at 20:36 Category: Developer CVS

[Savannah-help-public] Re: Project description page

Andrea Pescetti wrote: > On 28/10/2007 Yavor Doganov wrote: > > The agreed standard location was > > http://www.gnu.org/server/standards/translations/$project/ > > ...but TTBOMK we're still waiting for the Savannah hackers to ack > > whether this could be done. &

[Savannah-help-public] [sr #106056] Cannot request to join the "GNU make" group

Follow-up Comment #1, sr #106056 (project administration): I encountered the same problem some time ago but forgot to report it to the Savannah Hackers. My workaround is to include more (key)words from the project's long and short description, e.g. searching for "make executables" instead of onl

[Savannah-help-public] [sr #105902] Passing my savannah admin rights to yavor

Follow-up Comment #2, sr #105902 (project administration): Thank you, Sylvain. Of course it is much better to do as you suggest. Should I contact you at #savannah-hackers when the time comes or there is a different procedure? Is there any documentation that I must read? __

[Savannah-help-public] [sr #105801] Changes to the CVS tree of "www" do not propagate to www.gnu.org

URL: Summary: Changes to the CVS tree of "www" do not propagate to www.gnu.org Project: Savannah Administration Submitted by: yavor Submitted on: Friday 03/16/2007 at 13:14 Catego

[Savannah-help-public] [sr #105528] Deal with encoding issues in log_accum

Follow-up Comment #6, sr #105528 (project administration): Thank you very much. Here's a link: http://zver.fsa-bg.org/pipermail/dict-notifications/2006-October/000338.html ___ Reply to this item at:

[Savannah-help-public] [sr #105528] Please enable commit logs for the `www-bg' project

Follow-up Comment #4, sr #105528 (project administration): If this is a general setting that affects all projects, I completely agree. But if it's possible to make this change only for "www-bg", I kindly ask you to do so. Our diffs and commit messages are always in UTF-8, so people that are usi

[Savannah-help-public] [sr #105528] Please enable commit logs for the `www-bg' project

Follow-up Comment #2, sr #105528 (project administration): Unfortunately it seems that the messages are coming with "Content-Type: text/plain; charset=iso-8859-1" header which make them unreadable. Some prominent MUAs like Mutt and Gnus can handle this and show them with a proper encoding, but o

[Savannah-help-public] [sr #105528] Please enable commit logs for the `www-bg' project

URL: Summary: Please enable commit logs for the `www-bg' project Project: Savannah Administration Submitted by: yavor Submitted on: Friday 08/25/2006 at 17:54 Category: Developer