On Aug 13, 2012, at 22:56, Andreas Barth wrote:
> * Stefano Zacchiroli (lea...@debian.org) [120813 20:39]:
>> - If you are currently a (delegated) Policy editor, please reconfirm
>> your interest in such a role, by mailing me and/or this list. (For the
>> avoidance of doubt, I'm Bcc:-ing all cu
On Jun 26, 2009, at 20:14, Russ Allbery wrote:
The hard work is taking a proposal for a concrete change, thinking
through all the implications, getting buy-in from the affected people,
and then writing a section of Policy for it that clearly communicates
the issue. Secondarily, we need more re
On Jun 26, 2009, at 19:27, Steve Langasek wrote:
On Fri, Jun 26, 2009 at 05:09:00PM +0200, Jeremiah Foster wrote:
I am also cautious about wiki'ising this manual. I'd rather we go
through a more cautious process of agreeing the wording and ensuring
the detail is clear to all reader
On Jun 26, 2009, at 19:00, Russ Allbery wrote:
"In all cases, the part of the field contents on the same line as the
field name, is empty."
The second comma here *would* be a grammatical error. You cannot
separate the noun from the verb with a comma.
Not according to Strunk and White. The
On Jun 26, 2009, at 16:15, Lesley Binks wrote:
2009/6/26 Jeremiah Foster :
Hello,
On this page:
http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Files
one
can see the following sentence under "5.6.21 Files"
"In all cases the pa
Hello,
On this page: http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Files
one can see the following sentence under "5.6.21 Files"
"In all cases the part of the field contents on the same line as the
field name is empty."
This syntax is rather garbled. I'd like to pr
On Jun 24, 2009, at 8:22, Ben Finney wrote:
Jonathan Yu writes:
For me it just seems odd to add fields to d/control that aren't in
policy, though your explanation makes sense to me.
Debian policy is, ideally, descriptive instead of proscriptive. In
other
words, it (ideally) changes only
7 matches
Mail list logo
