[sr #110884] Don't present blank Originator Name: and Originator Email:

2023-06-02 Thread INVALID.NOREPLY
Follow-up Comment #3, sr #110884 (project administration): All I know is that even when looged in, these fields are blank. ___ Reply to this item at: ___

[sr #110884] Don't present blank Originator Name: and Originator Email:

2023-06-02 Thread INVALID.NOREPLY
Additional Item Attachment, sr #110884 (project administration): File name: 20230602T115738.jpgSize:143 KB ___ Reply to this item at:

[sr #110592] Privacy: Please don't include IP and UserAgent in email headers

2022-01-22 Thread INVALID.NOREPLY
Follow-up Comment #6, sr #110592 (project administration): Thank you :) The other thing I just recognized is that all the recipients are listed within the To: header. Maybe the frontend could instead use BCC to make it impossible to harvest private mail addresses by just adding an own address to

[sr #110592] Privacy: Please don't include IP and UserAgent in email headers

2022-01-01 Thread INVALID.NOREPLY
Follow-up Comment #4, sr #110592 (project administration): I don't see a point in the whole "# User details." block. If the savannah frontend has been used to create spam in the past it should be catched before actually sending the mail (limiting notifications for new users, denying them to add m

[sr #110592] Privacy: Please don't include IP and UserAgent in email headers

2021-12-31 Thread INVALID.NOREPLY
Follow-up Comment #2, sr #110592 (project administration): I am talking about the notification emails sent from savannah.gnu.org and savannah.nongnu.org. Including the email just sent by this very comment and the email I got to notify me about your comment. I should have mentioned that before. So

[sr #110592] Privacy: Please don't include IP and UserAgent in email headers

2021-12-31 Thread INVALID.NOREPLY
URL: Summary: Privacy: Please don't include IP and UserAgent in email headers Project: Savannah Administration Submitted by: consolatis Submitted on: Sat 01 Jan 2022 04:53:04 AM UTC

[sr #110553] Allow fetch of specific commit hash from git://git.sv.gnu.org

2021-11-05 Thread INVALID.NOREPLY
Follow-up Comment #7, sr #110553 (project administration): [comment #5 comment #5:] > AFAIK https://git.savannah.gnu.org/git lists all Git repositories on Savannah. This feature is managed separately for each repository. I didn't turn it all for all Savannah repositories because I wasn't sure th

[sr #110553] Allow fetch of specific commit hash from git://git.sv.gnu.org

2021-10-27 Thread INVALID.NOREPLY
Follow-up Comment #4, sr #110553 (project administration): I've also noticed that this issue exists for the git server at https://git.savannah.gnu.org/git as well. I assumed they were the same git server. Would it be possible to add the configuration change to this git server as well? ___

[sr #110553] Allow fetch of specific commit hash from git://git.sv.gnu.org

2021-10-22 Thread INVALID.NOREPLY
Follow-up Comment #3, sr #110553 (project administration): Yes, much faster than cloning. I've confirmed that the changes do work. The checkout is now under 1 minute. Thank you! root@debian:~/gnulib-test# git -C gnulib remote add origin git://git.sv.gnu.org/gnulib root@debian:~/gnulib-test# time

[sr #110553] Allow fetch of specific commit hash from git://git.sv.gnu.org

2021-10-21 Thread INVALID.NOREPLY
Follow-up Comment #1, sr #110553 (project administration): For some numbers, not in a VM, but on a laptop, the clone takes about 5 minutes, but the fetch shallow fetch takes about 1 minute. On the qemu VM (with 2G of memory) its 42 minutes(!!) for the clone and 20 seconds total for the shallow fe

[sr #110553] Allow fetch of specific commit hash from git://git.sv.gnu.org

2021-10-20 Thread INVALID.NOREPLY
URL: Summary: Allow fetch of specific commit hash from git://git.sv.gnu.org Project: Savannah Administration Submitted by: g10 Submitted on: Thu 21 Oct 2021 06:33:22 AM UTC Cat

[sr #110452] Deletion request

2021-02-28 Thread INVALID.NOREPLY
URL: Summary: Deletion request Project: Savannah Administration Submitted by: frnmst Submitted on: Sun 28 Feb 2021 11:22:31 PM CET Category: None Priority: 5 -

[sr #110433] Can you remove my account?

2021-01-24 Thread INVALID.NOREPLY
URL: Summary: Can you remove my account? Project: Savannah Administration Submitted by: goodnewseveryone Submitted on: Вс 24 янв 2021 09:41:02 Category: None Pr

[sr #110098] Can't be logged in on certain pages

2019-11-07 Thread INVALID.NOREPLY
Follow-up Comment #5, sr #110098 (project administration): Well no other site has a "clean reload" button. That's because I'm sorry to say there is something wrong with this site. E.g., reading this bug, I see I am logged in. But opening http://savannah.nongnu.org/bugs/?group=mhonarc in another wi

[sr #110098] Can't be logged in on certain pages

2019-11-05 Thread INVALID.NOREPLY
Follow-up Comment #2, sr #110098 (project administration): OK, here's what I finally did: Login on the savannah home page. In the search box search for MHonArc. Ah, finally got there still logged in! Now I can enter my MHonArc bug. ___ Repl

[sr #110098] Can't be logged in on certain pages

2019-11-05 Thread INVALID.NOREPLY
Follow-up Comment #1, sr #110098 (project administration): P.S., even though there is uri=%2Fbugs%2F%3Fgroup%3Dmhonarc but I am redirected to https://savannah.nongnu.org/my/ instead. Chromium on Debian. ___ Reply to this item at:

[sr #110098] Can't be logged in on certain pages

2019-11-05 Thread INVALID.NOREPLY
URL: Summary: Can't be logged in on certain pages Project: Savannah Administration Submitted by: jidanni Submitted on: Wed 06 Nov 2019 03:32:55 AM UTC Category: Savannah websit

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

2008-10-12 Thread INVALID.NOREPLY
Follow-up Comment #5, sr #106473 (project administration): Any news here? I just added a comment to my submission and found this support entry after that. Must have missed reading it. I would also like to use Savannah, because I think Sourceforge is too fat for me as small project, BerliOS seems