Valery Ushakov wrote:
> I think that information *must* be there, as that's *the* place where
> the names are (un)parsed. I'm not sure whether this information has
> to be duplicated as-is in chflags(1), or whether chflags(1) can have a
> less verbose version.
Perhaps a simple
See stat_flags(3
On Thu, May 25, 2023 at 09:59:41 -0400, Greg Troxel wrote:
> Taylor R Campbell writes:
>
> > jschauma@'s change did help clarify (1) and (2). Let's try to work
> > together to make it better?
[...]
> I would recommend:
>
> Noting that archive flag represents something in some foreign
> fi
Date:Thu, 25 May 2023 09:59:41 -0400
From:Greg Troxel
Message-ID:
| Also, the man page does not explain that because "nodump" is the name of
| a flag, one does "chflags dump foo" to remove the nodump flag.
It doesn't really need to, as while that works, so does
Taylor R Campbell writes:
> jschauma@'s change did help clarify (1) and (2). Let's try to work
> together to make it better?
Well said.
I can shed a little light on some of the questions.
> 1. What is `arch' or `archived' supposed to mean? Who sets it, who
>pays attention to it, and wha
> Date: Thu, 25 May 2023 15:10:41 +0300
> From: Valery Ushakov
>
> This new paragraph is wedged right between the list of the options and
> the continuation of that same paragraph that says that they can be
> prefixed with "no".
>
> A description of an obsolete flag right in the middle of the ma
Valery Ushakov wrote:
> Anyway, this change is strictly for the worse.
¯\_(ツ)_/¯
I've reverted the change.
-Jan
Valery Ushakov writes:
> On Thu, May 25, 2023 at 07:17:52 -0400, Greg Troxel wrote:
>
>> Jan Schaumann writes:
>>
>> > Valery Ushakov wrote:
>> >> On Wed, May 24, 2023 at 22:33:17 +, Jan Schaumann wrote:
>> >
>> >> > Briefly describe the 'arch' and 'nodump' flags.
>> >>
>> >> What makes t
On Thu, May 25, 2023 at 07:17:52 -0400, Greg Troxel wrote:
> Jan Schaumann writes:
>
> > Valery Ushakov wrote:
> >> On Wed, May 24, 2023 at 22:33:17 +, Jan Schaumann wrote:
> >
> >> > Briefly describe the 'arch' and 'nodump' flags.
> >>
> >> What makes them special and why is that these tw
On Wed, May 24, 2023 at 23:44:07 -0400, Jan Schaumann wrote:
> Valery Ushakov wrote:
> > On Wed, May 24, 2023 at 22:33:17 +, Jan Schaumann wrote:
>
> > > Briefly describe the 'arch' and 'nodump' flags.
> >
> > What makes them special and why is that these two have to be described
> > here a
Jan Schaumann writes:
> Valery Ushakov wrote:
>> On Wed, May 24, 2023 at 22:33:17 +, Jan Schaumann wrote:
>
>> > Briefly describe the 'arch' and 'nodump' flags.
>>
>> What makes them special and why is that these two have to be described
>> here and not in chflags(2), where the flags are ac
Valery Ushakov wrote:
> On Wed, May 24, 2023 at 22:33:17 +, Jan Schaumann wrote:
> > Briefly describe the 'arch' and 'nodump' flags.
>
> What makes them special and why is that these two have to be described
> here and not in chflags(2), where the flags are actually defined?
Unlike the othe
On Wed, May 24, 2023 at 22:33:17 +, Jan Schaumann wrote:
> Module Name: src
> Committed By: jschauma
> Date: Wed May 24 22:33:17 UTC 2023
>
> Modified Files:
> src/usr.bin/chflags: chflags.1
>
> Log Message:
> Briefly describe the 'arch' and 'nodump' flags.
What makes them sp
12 matches
Mail list logo
