On Wed, 27 Jul 2022 16:10:18 +0200, Wouter Verhelst
wrote:
>On Mon, Jul 25, 2022 at 07:06:59PM +0200, Marc Haber wrote:
>> I don't like the idea of messing with old NEWS entries at all.
>
>I'm trying to understand why you feel this way.
It feels like rewriting history. Maybe the similiarity of
On Mon, Jul 25, 2022 at 07:06:59PM +0200, Marc Haber wrote:
> I don't like the idea of messing with old NEWS entries at all.
I'm trying to understand why you feel this way.
A NEWS.Debian entry is not aimed towards developers; it is meant as
documentation shown to the user when upgrading. Having
On Mon, 25 Jul 2022 09:05:55 -0700, Josh Triplett
wrote:
>Matt Barry wrote:
>> On Mon, 2022-07-25 at 14:37 +0100, Colin Watson wrote:
>> > On Sun, Jul 24, 2022 at 12:34:31PM -0400, Matt Barry wrote:
>> > > Anyway, its been released at this point, so the issue is moot :)
>> >
>> > Regardless of
Matt Barry wrote:
> On Mon, 2022-07-25 at 14:37 +0100, Colin Watson wrote:
> > On Sun, Jul 24, 2022 at 12:34:31PM -0400, Matt Barry wrote:
> > > Anyway, its been released at this point, so the issue is moot :)
> >
> > Regardless of the rest of the discussion, this isn't entirely true.
> > Yes,
On Mon, 2022-07-25 at 14:37 +0100, Colin Watson wrote:
> On Sun, Jul 24, 2022 at 12:34:31PM -0400, Matt Barry wrote:
> > Anyway, its been released at this point, so the issue is moot :)
>
> Regardless of the rest of the discussion, this isn't entirely true.
> Yes, people following unstable will
On Sun, Jul 24, 2022 at 12:34:31PM -0400, Matt Barry wrote:
> Anyway, its been released at this point, so the issue is moot :)
Regardless of the rest of the discussion, this isn't entirely true.
Yes, people following unstable will have already seen the NEWS entry and
apt-listchanges won't show it
On Mon, 2022-07-25 at 09:33 +0200, Bjørn Mork wrote:
> Philipp Kern writes:
> > On 25.07.22 08:46, Bjørn Mork wrote:
> > >
> > > obviously false. "No change" is always less surprising than any
> > > change,
> > > whatever the rationale is.
> >
> > It can also be unsurprising from an end-user's
Philipp Kern writes:
> On 25.07.22 08:46, Bjørn Mork wrote:
>> Matt Barry writes:
- why has a change been made
>>>
>>> I think this is explained in excruciating detail. The short version
>>> (from NEWS):
>>>
>>> "mode 0700 provides both the most secure, unsurprising default"
> [...]
>> And
On 25.07.22 08:46, Bjørn Mork wrote:
Matt Barry writes:
- why has a change been made
I think this is explained in excruciating detail. The short version
(from NEWS):
"mode 0700 provides both the most secure, unsurprising default"
[...]
And the claim that this is "most unsurprising" (less
Matt Barry writes:
>> - why has a change been made
>
> I think this is explained in excruciating detail. The short version
> (from NEWS):
>
> "mode 0700 provides both the most secure, unsurprising default"
This is a self-referencing explanation. It provides no value. It's
only good if you
Hello,
On Sun, 2022-07-24 at 15:09 +0100, RL wrote:
> Marc Haber writes:
>
> > ... Here is what the adduser team considers possible
> > documentation for this, and we itend to include this in NEWS.Debian
> > as a
> > rationale for the change.
>
> As a user who reads NEWS.Debian (via
Marc Haber writes:
> ... Here is what the adduser team considers possible
> documentation for this, and we itend to include this in NEWS.Debian as a
> rationale for the change.
As a user who reads NEWS.Debian (via apt-listchanges) i found the text
didnt give me the answers i was looking for. I
12 matches
Mail list logo
