[sr #111026] AGPL spamming my `git pull` outputs

Update of sr#111026 (group administration): Status: In Progress => Done ___ Reply to this item at: _

[sr #111026] AGPL spamming my `git pull` outputs

Follow-up Comment #12, sr#111026 (group administration): [comment #11 comment #11:] > > The issue has been resolved for the git server. > > I confirm that it seems to be sane again, thank you. Same here. Thanks. ___ Reply to this item a

[sr #111026] AGPL spamming my `git pull` outputs

Update of sr#111026 (group administration): Open/Closed:Open => Closed ___ Reply to this item at: _

Re: Extremely large change wave?

Ineiev wrote: > Bob Proulx wrote: > > I am trying to understand the large change wave that has been > > committed in the last few days. > > Last quite a few months, in a sense. the date of 9fd58ef254ab is > 2023-08-16. On February 8th I made a commit fixing (partially) a critical bug. Then through

[sr #111026] AGPL spamming my `git pull` outputs

Follow-up Comment #11, sr#111026 (group administration): > The issue has been resolved for the git server. I confirm that it seems to be sane again, thank you. ___ Reply to this item at:

Re: How to build savane now?

Ineiev wrote: > Bob Proulx wrote: > > These are the things that we need to be able to do. > > > > * Build a local copy of savane > > INSTALL is expected to cover this; is there anything > that doesn't work for you, specifically? I don't think anyone was previously aware of the recent changes to IN

[sr #111026] AGPL spamming my `git pull` outputs

Follow-up Comment #10, sr#111026 (group administration): The issue has been resolved for the git server. https://savannah.nongnu.org/support/?111026 ___ Reply to this item at: ___

License spamming issue resolved

The license spamming issue has been going on for way too long. Literally months people have been complaining. It's a real problem. It should have been fixed long ago. Timed out. The issue has been resolved by removing sv_membersh from the process flow. Custom programming is not required for thi

Re: [sr #111026] AGPL spamming my `git pull` outputs

On Tue, Feb 27, 2024 at 09:27:58AM -0500, Stefan Monnier wrote: > > How does the script tell which connection is interactive? > > Usually that's done by testing if the output is a tty. user@host:~$ ssh ine...@cfarm110.cfarm.net cat tty.pl #! /usr/bin/perl print "tty(?)\n" if -t 1; print "scripted

Re: [sr #111026] AGPL spamming my `git pull` outputs

> How does the script tell which connection is interactive? Usually that's done by testing if the output is a tty. Stefan

Re: [sr #111026] AGPL spamming my `git pull` outputs

On Tue, Feb 27, 2024 at 08:05:42AM -0500, Stefan Monnier wrote: > > I see no reason why it needs to display the notice on every connection, > including those whose output is processed by a program ... > I already suggested we can display it only on interactive connections. How does the script tel

Re: [sr #111026] AGPL spamming my `git pull` outputs

> [comment #7 comment #7:] >> The AGPL itself does not require this kind of notice, as far as I can tell, > The AGPL requires that the program in question prominently offer every its > user the corresponding source code; I believe the current implementation > complies with that, and rms has confirm