Fair question. I could not find an answer to that in the history so I have reopened it. At a minimum I think we should document the rationale for closing and put a status on the ticket that reflects
Follow-up Comment #19, sr #106712 (project administration): May I add my voice to those desiring such a feature? It's much easier to reply by writing an email than to use the Savannah web interface.
Follow-up Comment #18, sr #106712 (project administration): Dropping the Savane trackers means migrating all the data and recreate other features such as integrated authentication. We're moving towar
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 consi
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
Follow-up Comment #15, sr #106712 (project administration): there is a dupe for this: sr #107431 any chance this will be implemented? actually, it would seen that dropping the integrated savanna bug
Follow-up Comment #13, sr #106712 (project administration): I think every few minutes would be ok, though not ideal. At any rate, I'm afraid I have no clue how to implement anything like this in php.
Follow-up Comment #12, sr #106712 (project administration): Karl, i have no idea of how the cgi call could be done to perform the instant handling of messages. The only solution that comes to my mind
Follow-up Comment #11, sr #106712 (project administration): I realized last night that savannah doesn't handle incoming mail locally, as far as I know. So I don't see how the mail handling and web ap
Follow-up Comment #10, sr #106712 (project administration): Karl -- i think that if both the program that handles the messages and the web application run in the same host there wouldn't be any probl
Follow-up Comment #9, sr #106712 (project administration): Thomas -- I don't see a problem with requiring logged-in users to post or follow up. In fact, I think that should be the default. There is n
Follow-up Comment #8, sr #106712 (project administration): Federico -- the idea of doing a POST as if it were done through the web site sounds good. If we can somehow fake the session information it
Follow-up Comment #7, sr #106712 (project administration): For the the server-side part i believe that one possible implementation could be the following: 1.- Set up a cronjob, following the structur
Follow-up Comment #6, sr #106712 (project administration): Karl: But only allowing logged-in users to post follow-ups, wouldn't that be contradictionary to allowing non-subscribers post to GNU mailin
Follow-up Comment #5, sr #106712 (project administration): To the best of my knowledge, it is possible to configure trackers such that only logged-in users can post or follow-up. At least I sure reme
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. T
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 woul
Follow-up Comment #2, sr #106712 (project administration): Right, we could devise some reasonable format for the messages and I guess that would exclude the spam. We don't need nearly all the bells a
Follow-up Comment #1, sr #106712 (project administration): Hi, I have always found this very interesting (sending a mail with instructions to one machine), but probably i don't have the required skil