Quoting Otto Kekäläinen (2025-06-01 08:07:01)
> Your reply had:
>
> To: 972695-qu...@bugs.debian.org,
> 972695-submit...@bugs.debian.org, Yadd
>
> I am wondering did you add this 972695-qu...@bugs.debian.org manually
> or was it in the Reply-To headers? In this case it would have been
> best
Hi!
> Arguably, such setup is spam: I is a bot that messes with the bugs but
> is not accountable for its actions, since it is only a one-way
> communication. Sure, I can then investigate the email and figure out
> which non-email side channel might reach the true originator of the
> bot activity,
On Sat, 31 May 2025 20:17:59 +0200, Santiago Vila
wrote:
>I don't see a big problem in those messages being "noreply",
>considering that they are generated automatically,
Answers to these messages shouldnt result in a generic bounce.
Greetings
Marc
--
---
El 31/5/25 a las 21:41, Jonas Smedegaard escribió:
That's an automatically triggered message created by a gitlab hook,
which parses the commit message for "closes: #n" and notifies the bug
submitter when it's known that the bug is fixed in salsa.
The problem is that the confident submitter
Hello fellow developers,
On Sun, Apr 13, 2025 at 05:25:59PM +0200, Helmut Grohne wrote:
> All of the perl ones have been filed and gregor already fixed (thanks!)
> a significant fraction including all 11 perl-xs-dev ones. I
> guess that on third of these is fixed in git or unstable.
I guess half
Quoting Santiago Vila (2025-05-31 20:17:59)
> El 31/5/25 a las 18:19, Jonas Smedegaard escribió:
> > The concrete incidence is https://bugs.debian.org/972695#28
> >
> > Am I missing something sensible here, or do others also see a problem
> > in this setup?
> That's an automatically triggered mess
El 31/5/25 a las 18:19, Jonas Smedegaard escribió:
The concrete incidence is https://bugs.debian.org/972695#28
Am I missing something sensible here, or do others also see a problem
in this setup?
That's an automatically triggered message created by a gitlab hook,
which parses the commit message
I received an update to a bugreport, but responding to it bounced.
I don't know if this is a one-off experiment or a common setup, but
I find it bad for Salse to inject automated emails to Debbugs: Debbugs
is supposed to be usable with email interaction.
Arguably, such setup is spam: I is a bot t
Hi Philipp, hi all,
> On Sat, 31 May 2025 15:11:11 +0200, Philipp Kern said:
> But to me the weirdest thing is that quite a few complained and there
> was no real response rationalizing the decision.
You may have missed this email
https://lists.debian.org/debian-www/2025/05/msg00022
Hello Philipp,
Am Sat, May 31, 2025 at 03:11:11PM +0200 schrieb Philipp Kern:
> On 5/9/25 1:45 AM, Antonio Terceiro wrote:
> > On Thu, May 08, 2025 at 10:33:55PM +0200, Holger Wansing wrote:
> >> I think about removing myself from the debian-www team.
> >> Better no longer be part of it, otherwise
On 5/9/25 1:45 AM, Antonio Terceiro wrote:
> On Thu, May 08, 2025 at 10:33:55PM +0200, Holger Wansing wrote:
>> I think about removing myself from the debian-www team.
>> Better no longer be part of it, otherwise people might blame me for such
>> decisions ...
>
> Please don't. Breaking things i
Il 31/05/2025 07:34, Marc Haber ha scritto:
On Fri, 30 May 2025 13:28:26 -0700, Soren Stoutner
wrote:
You can also edit your general notification settings, but if you are a Debian
Developer (and thus a member of the Salsa Debian team) that would mean you
would receive notifications for every pa
12 matches
Mail list logo
