> "Henning" == Henning Makholm <[EMAIL PROTECTED]> writes:
Henning> I stand corrected, apparently. (But I have yet to imagine which
Henning> arguments would be used against doing a release if we happen to
Henning> find testing in a freezeable state 6 months after sarge
Henning>
> "Jonathan" == Jonathan Dowland <[EMAIL PROTECTED]> writes:
Jonathan> On Tue, Dec 02, 2003 at 12:08:17PM +0100, Andreas Metzler
Jonathan> wrote:
>> Afaik: 2.4.23 contains literally 100s of changes, one of these was a
>> small change to do_brk(), which looked like a normal non-
> "Scott" == Scott James Remnant <[EMAIL PROTECTED]> writes:
Scott> You've never had to combine 'patch' and Python programs have you?
Scott> After receiving a few created by people with different indent
Scott> bigotries you quickly realise why significant whitespace is a
Scott>
> "Wouter" == Wouter Verhelst <[EMAIL PROTECTED]> writes:
Tom> Significant whitespace? Shudder, that brings back crusty old
Tom> memories of Fortran. I have great fondness for fortran because of
Tom> the wonderful mathematical algorithms in LinPack, but I have no
Tom> fondnes
> "Tom" == Tom <[EMAIL PROTECTED]> writes:
Tom> Do whitespace mistakes cause compile time errors? The frustrating
Tom> thing about fortran was variable names that started with C could be
Tom> interpreted as comments not indented correctly, which would just
Tom> cause that lin
> "Tom" == Tom <[EMAIL PROTECTED]> writes:
Tom> Significant whitespace? Shudder, that brings back crusty old
Tom> memories of Fortran. I have great fondness for fortran because of
Tom> the wonderful mathematical algorithms in LinPack, but I have no
Tom> fondness for signific
> "H" == H S Teoh <[EMAIL PROTECTED]> writes:
H> I have a hate-hate relationship with it. I much prefer free-style
H> syntax where the programmer is allowed to use his best judgment on
H> how to indent the code. Of course, in less-than-ideal projects, or
H> projects with less-t
> "H" == H S Teoh <[EMAIL PROTECTED]> writes:
H> That would mean 95% of non-trivial XSLT stylesheets would need to be
H> rewritten...
Or perhaps the XSLT language itself needs to be rewritten.
Regards,
Isaac.
> "Daniel" == Daniel Jacobowitz <[EMAIL PROTECTED]> writes:
Daniel> On Mon, Nov 10, 2003 at 07:17:13PM -0800, Mike Fedyk wrote:
>> On Sat, Nov 08, 2003 at 06:43:09PM +0100, Robert Millan wrote: > And
>> Nikita just pointed out there's libc6-i686. It might make sense to
>> add >
> "Martin" == Martin Godisch <[EMAIL PROTECTED]> writes:
Martin> What's the preferred way to do this check? Consider, some shell
Martin> is installed with its appropriate entry in /etc/shells. Now, we
Martin> remove it: the entry will be deleted from /etc/shells, which
Martin>
> "cobaco" == cobaco <[EMAIL PROTECTED]> writes:
cobaco> Basically, it's the difference between having a sysadmin
cobaco> spending fifteen minutes every day or week tweaking your server
cobaco> to keep it running, or having a sysadmin come in for a week once
cobaco> a year to
> "cobaco" == cobaco <[EMAIL PROTECTED]> writes:
cobaco> kde 3.2 release is slated for 8th december[1], is there any
cobaco> chance we'll wait for it, just so the outdated kde label doesn't
cobaco> apply again immediately after release?
But does the first few paragraphs of RM's o
> "Brian" == Brian May <[EMAIL PROTECTED]> writes:
Brian> Couldn't you write a new document along the lines of "This is
Brian> based on RFC1341 with the following exceptions "?
Brian> That way you can see exactly what differences there are to the
Brian> known standard, at
> "Jérôme" == Jérôme Marant <[EMAIL PROTECTED]> writes:
Jérôme> But we absolutely don't want to do this.
Jérôme> It is just like modifying someone else' speach and
Jérôme> redistributing it without changing the author's name.
Jérôme> It is obvious it should be out of the scop
> "Eduard" == Eduard Bloch <[EMAIL PROTECTED]> writes:
Eduard> And do we know this? Why not trying to talk with other
Eduard> distributors to try to coordinate our efforts. When they are too
Eduard> arogant and continue doing cludges, then we can put this in the
Eduard> Debian-
15 matches
Mail list logo
