On Sun, 2024-01-28 at 17:10 +, Ineiev wrote:
> Fixed, sorry for the trouble.
Looks great, thanks!
On Sat, 2024-01-27 at 16:04 -0600, G. Branden Robinson wrote:
> At 2024-01-27T16:51:29-0500, Paul Smith wrote:
> > Is anyone else seeing this strange formatting of the "Post a
> > comment" section on Savannah? I attach a screenshot of what
> > happens when I clic
Is anyone else seeing this strange formatting of the "Post a comment"
section on Savannah? I attach a screenshot of what happens when I
click the "(+)" next to the section title to add a new comment.
Is this the intended display result?
I'm using Firefox 121.0.1 on GNU/Linux x86_64.
--
Paul
Is it just me or has anyone else noticed that there are no graphics
(just broken icon images) for the various icons on Savannah home pages?
I've looked at a few.
For example: https://savannah.gnu.org/projects/make/
Hm, now that I look, it seems that if I visit the page in an incognito
window
On Sun, 2022-10-23 at 13:13 -0400, Ian Kelling wrote:
> There was an error on the mail server I overlooked. It is fixed now
> and mail is working its way through the queue. Sorry, I've been
> working on speeding up overall mail delivery, and some of the changes
> have caused unfortunate delays as
On Sat, 2022-10-22 at 09:35 +0300, Eli Zaretskii wrote:
> > Thanks, I will report any significant problems if I see them.
>
> I have now seen a message that was delayed by 2 hours and 50 minutes.
> Would you like me to post it, or any parts of it that might be of
> interest?
I've sent a number
On Tue, 2022-09-20 at 09:35 -0400, Paul Smith wrote:
> Is the hook for sending email on commits to git.sv.gnu.org working?
>
> I pushed a change this morning and didn't see any email about it.
>
> Cheers!
Got the email about 4 hours later; apparently there's some lag in the
sys
Is the hook for sending email on commits to git.sv.gnu.org working?
I pushed a change this morning and didn't see any email about it.
Cheers!
On Sun, 2022-08-14 at 22:06 -0600, Bob Proulx wrote:
> Paul Smith wrote:
> > I haven't been able to reach the Savannah website for most of the
> > day.
> > Things like the Git service are available but the website is not.
>
> Thanks for the report. It appears t
I haven't been able to reach the Savannah website for most of the day.
Things like the Git service are available but the website is not.
On Tue, 2017-02-07 at 14:04 -0700, Bob Proulx wrote:
> I switched git dns over to the new server (again) this morning.
> Trying not to thrash the IP address for git+ssh users too often.
> Everything git core command specific looks okay for my testing.
I was able to use the new server without any
On Fri, 2017-02-03 at 19:35 -0700, Bob Proulx wrote:
> Note that this isn't a migration problem. I pulled git back to the
> older server. So it might be a problem with the older git version on
> the older server.
I don't want to interrupt anyone's good work, but I wonder if there's a
hoped-for
On Mon, 2016-12-12 at 04:06 -0700, Bob Proulx wrote:
> On the good news side of things is that hopefully most people haven't
> noticed any huge disruption because of this. As soon as I work
> through the most recent problems then I will say something about https
> being available.
I've seen the
Hi all; very excited to see some new infrastructure being deployed for
Savannah!
I was wondering if the changes will allow us to address the current
problem where we don't have MitM-resistant access to SCM repositories
(at least not Git repositories) for non-maintainers; currently the only
On Fri, 2016-10-07 at 22:16 -0400, Mike Gerwitz wrote:
> On Mon, Sep 19, 2016 at 12:30:03 +0200, Hanno Böck wrote:
> > *The code repositories*
> >
> > Now all of the above can be aleviated a bit if a user carefully uses
> > https all the time manually or uses a plugin like https everywhere. But
>
On Fri, 2016-05-27 at 11:18 +0200, Aljosha Papsch wrote:
> > If the project is serious about enforcing these habits then the right
> > way to do it is by rejecting commits that don't meet the criteria, so
> > that the user can fix them and avoid incorrect commits appearing in the
> > repository in
On Thu, 2016-05-26 at 13:41 -0700, Jim Meyering wrote:
> On Tue, May 24, 2016 at 10:30 PM, Aljosha Papsch wrote:
> > Thanks for the clarification. I will fix these files now. While forcing
> > users to push clean files is unexpected for user, I guess it would be great
> > if these messages were
On Thu, 2015-11-05 at 12:54 -0700, Bob Proulx wrote:
> > > remote: File "/srv/git/emacs.git/hooks/git_multimail.py", line 1472, in
> > > send
> > > remote: p.terminate()
> > > remote: File "/usr/lib/python2.6/subprocess.py", line 1269, in terminate
> > > remote:
On Thu, 2015-11-05 at 22:12 +0200, Eli Zaretskii wrote:
> > Date: Thu, 5 Nov 2015 12:54:30 -0700
> > From: Bob Proulx
> > Cc: savannah-hackers-public@gnu.org
> >
> > > > remote: File "/srv/git/emacs.git/hooks/git_multimail.py", line 1472,
> > > > in send
> > > > remote:
Looking at http://git.savannah.gnu.org/cgit for GNU make (at least)
there's something bizarre about it:
http://git.savannah.gnu.org/cgit/make.git/tree
If I don't specify any tag or SHA in the URL, it always chooses some
strange commit from 2013 as the default; for example:
On Fri, 2014-03-28 at 12:18 -0600, Bob Proulx wrote:
Thank you for reporting this problem. However this always works fine
for me. But I think we have different environments. Does being
logged in versus not logged in change this in any way?
When I am logged in the page always redirects to
On Fri, 2013-03-01 at 15:45 +, Karl Berry wrote:
There are many hundreds of git processes happily chugging away on vcs,
going back to October. This can't be right?
Do you know what they're doing? Presumably they're all waiting on
something since if they were all active the server would be
So, I've decided that having separate trackers for bugs, support,
patches, and tasks is annoying and confusing. I'd like to consolidate
them all and have just one tracker: Bugs.
What I'd really like to do is move the patches and support tracker
contents into the bug tracker (the tasks tracker
On Mon, 2010-11-29 at 19:34 +0100, Sylvain Beucler wrote:
What I know is there's been a SQL injection leading to illegitimate
membership access
Oh blerg. The prevalence of these types of very simple (to avoid and to
fix) mistakes even on technical sites makes me despair.
OK thanks.
PS. I
There's a problem with the email notification code in Savannah.
Recently a bug was filed (http://savannah.gnu.org/bugs/?31614) in which
the verbatim tag was used to provide some code examples. In the bug,
the example looks correct:
$ echo 'a\ b:; echo $@' | make -f - a b
echo a b
Hi all;
This morning at about 1am EDT this user account:
https://savannah.gnu.org/users/sevanath
posted spam to 21 of the GNU make bug reports.
Please disable this account; thanks!
On Wed, 2010-07-28 at 21:16 +, Karl Berry wrote:
And changing this would require very significant discussion and effort
from the FSF sysadmins, since they are the only ones with the power to
actually make changes on the www.gnu.org server. I don't see that
happening any time in the
27 matches
Mail list logo