Manoj Srivastava writes ("Re: Locales and Programs parsing other's output"):
> I shall not be able to wqork on this over the weekend, but I
> was planning on looking at the policy manual and gleaning stuff from
> it. I intend ti have in the proposed manual things
Hi,
I shall not be able to wqork on this over the weekend, but I
was planning on looking at the policy manual and gleaning stuff from
it. I intend ti have in the proposed manual things that are required
by policy (files in /tmp was one issue); but after listening to the
people on this
On Thursday, April 16, Manoj Srivastava wrote
>
> I shall have to think about how far do we go, and how to limit
> the scope of this document. I do not think we can cover secure
> programming, portable programming, introduction to common softeware
> tools, historic bugs, I/O programming,
On Thu, Apr 16, 1998 at 06:36:28PM -0500, Manoj Srivastava wrote:
> Hi,
> >>"Marcus" == Marcus Brinkmann <[EMAIL PROTECTED]> writes:
>
> Marcus> Wow, I feel a document of high value and quality coming
> Marcus> up. This is my personal wishlist, as I'm truely an
> Marcus> unexperienced programmer:
> Manoj Srivastava <[EMAIL PROTECTED]> writes:
>
> > I shall have to think about how far do we go, and how to limit
> > the scope of this document. I do not think we can cover secure
> > programming, portable programming, introduction to common softeware
> > tools, historic bugs, I/O progra
Manoj Srivastava <[EMAIL PROTECTED]> writes:
> I shall have to think about how far do we go, and how to limit
> the scope of this document. I do not think we can cover secure
> programming, portable programming, introduction to common softeware
> tools, historic bugs, I/O programming, and
Hi,
>>"Marcus" == Marcus Brinkmann <[EMAIL PROTECTED]> writes:
Marcus> Wow, I feel a document of high value and quality coming
Marcus> up. This is my personal wishlist, as I'm truely an
Marcus> unexperienced programmer:
[SNIP]
Whooee, that's some list. I think we do want to think
On Wed, 15 Apr 1998, Ian Jackson wrote:
[snip]
> I'm beginning think we should split off the `standard programming
> requirements' that aren't Debian-specific into a separate manual. We
> could call it `Some specific issues for correct programming' or
> something.
[snip]
>
> Does anyone want to
On Wed, Apr 15, 1998 at 02:52:59PM -0500, Manoj Srivastava wrote:
> Hi,
> >>"Ian" == Ian Jackson <[EMAIL PROTECTED]> writes:
>
> Ian> Does anyone want to maintain this manual ? I take it from
> Ian> Christian's posting that he doesn't.
>
> I would be interested in (co-?) maintaining this
Manoj Srivastava writes ("Re: Locales and Programs parsing other's output"):
> >>"Ian" == Ian Jackson <[EMAIL PROTECTED]> writes:
> Ian> Does anyone want to maintain this manual ? I take it from
> Ian> Christian's posting that he doesn&
Hi,
>>"Ian" == Ian Jackson <[EMAIL PROTECTED]> writes:
Ian> Does anyone want to maintain this manual ? I take it from
Ian> Christian's posting that he doesn't.
I would be interested in (co-?) maintaining this manual, with
help from the list in determining what should or should not go in
Christian Schwarz writes ("Re: Locales and Programs parsing other's output"):
...
> There are some maintainers (including you) who always shout `this should
> be documented in policy'. If we would document everything in policy, I
> would be too busy with getting low
Christian Schwarz writes:
> I don't think this is a topic which belongs to the policy manual. (For
> example, the policy manual doesn't include a statement like `dereferencing
> NULL pointers is evil' either.)
>
> If we had a `Debian Programmer's Manual', this could go there--but since
> w
Christian Schwarz <[EMAIL PROTECTED]> writes:
> On 11 Apr 1998, James Troup wrote:
>
> > Christian Schwarz <[EMAIL PROTECTED]> writes:
> >
> > > I don't think this is a topic which belongs to the policy
> > > manual. (For example, the policy manual doesn't include a statement
> > > like `derefer
On 11 Apr 1998, James Troup wrote:
> Christian Schwarz <[EMAIL PROTECTED]> writes:
>
> > I don't think this is a topic which belongs to the policy
> > manual. (For example, the policy manual doesn't include a statement
> > like `dereferencing NULL pointers is evil' either.)
>
> Policy includes p
Christian Schwarz <[EMAIL PROTECTED]> writes:
> I don't think this is a topic which belongs to the policy
> manual. (For example, the policy manual doesn't include a statement
> like `dereferencing NULL pointers is evil' either.)
Policy includes plenty of examples of policies which potentially
re
(Sorry for the late reply.)
On Mon, 9 Mar 1998, Yann Dirson wrote:
> It appears that some programs in our distribution (see logs for bug
> #17361 or #19166 for known examples) are trying to parse other's
> output, without ensuring a specific locale.
>
> Such a behaviour can cause obscure failur
It appears that some programs in our distribution (see logs for bug
#17361 or #19166 for known examples) are trying to parse other's
output, without ensuring a specific locale.
Such a behaviour can cause obscure failures (eg. dpkg-parsechangelog
in #17361), or even erroneous output (the 'isnative
18 matches
Mail list logo
