Seems to have crashed, we don't know the cause yet. Is there anyone who is
dependent on this tonight? If so I'll drive down and fix it (yeah, very lame
of us, we moved it to a different rack which was too far away from our remote
power so I can't power cycle it remotely. Our bad.)
Let me know, if I don't hear from anyone we'll get it in about 14 hours. If
that's too long I'll understand, it's 20 minutes away and I can go deal.
--lm
On 2005-04-12, at 04:17, Larry McVoy wrote whatever...
Excuse me, but: who gives a damn shit?
tis 2005-04-12 klockan 13:10 +0200 skrev Marcin Dalecki:
> On 2005-04-12, at 04:17, Larry McVoy wrote whatever...
>
> Excuse me, but: who gives a damn shit?
>
Anyone who wants to have access to the history or any other functioning
of the repository.
Please don't pollute this list nor Larry with such comments.
El Tue, 12 Apr 2005 13:10:12 +0200,
Marcin Dalecki <[email protected]> escribi?:
>
> On 2005-04-12, at 04:17, Larry McVoy wrote whatever...
>
> Excuse me, but: who gives a damn shit?
All the kernel hackers who used BK for years and are still using it, I'd guess.
On Tue, 12 Apr 2005, Marcin Dalecki wrote:
>
> On 2005-04-12, at 04:17, Larry McVoy wrote whatever...
>
> Excuse me, but: who gives a damn shit?
>
Lots of people do; those who use bitkeeper, and even people (like me) who
don't use it to manage source but still use the info at bkbits.net to
track what patches got merged etc.
Ohh and by the way, Larry doesn't deserve comments like that. He's done a
lot of hard work for everyone here (not to mention spent a lot of money)
and he's provided an excellent tool. He deserves gratitude and respect,
not childish BS like the above.
--
Jesper Juhl
On Tue, Apr 12, 2005 at 05:19:34PM +0200, Jesper Juhl wrote:
> On Tue, 12 Apr 2005, Marcin Dalecki wrote:
> > On 2005-04-12, at 04:17, Larry McVoy wrote whatever...
> >
> > Excuse me, but: who gives a damn shit?
>
> Lots of people do; those who use bitkeeper, and even people (like me) who
> don't use it to manage source but still use the info at bkbits.net to
> track what patches got merged etc.
>
> Ohh and by the way, Larry doesn't deserve comments like that. He's done a
> lot of hard work for everyone here (not to mention spent a lot of money)
> and he's provided an excellent tool. He deserves gratitude and respect,
> not childish BS like the above.
I agree wholeheartedly.
But... I think someone is trolling here.
I mean: who makes a spelling error in his own first name? ;-)
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
On Tue, 12 Apr 2005, Toon van der Pas wrote:
> On Tue, Apr 12, 2005 at 05:19:34PM +0200, Jesper Juhl wrote:
> > On Tue, 12 Apr 2005, Marcin Dalecki wrote:
> > > On 2005-04-12, at 04:17, Larry McVoy wrote whatever...
> > > Excuse me, but: who gives a damn shit?
> >
> > Lots of people do; those who use bitkeeper, and even people (like me) who
> > don't use it to manage source but still use the info at bkbits.net to
> > track what patches got merged etc.
> >
> > Ohh and by the way, Larry doesn't deserve comments like that. He's done a
> > lot of hard work for everyone here (not to mention spent a lot of money)
> > and he's provided an excellent tool. He deserves gratitude and respect,
> > not childish BS like the above.
>
> I agree wholeheartedly.
>
> But... I think someone is trolling here.
> I mean: who makes a spelling error in his own first name? ;-)
I don't think so: both `c' and `t' are (different) ASCII-transcripts of the
actual non-ASCII character that should have been there. Yes, UTF-8 to US-ASCII
is lossy and imprecise ;-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Hi Geert,
you wrote on 13 Apr 2005:
> I don't think so: both `c' and `t' are (different) ASCII-transcripts of the
> actual non-ASCII character that should have been there. Yes, UTF-8 to US-ASCII
> is lossy and imprecise ;-)
There is now UTF there :-)
Both Marcin and Martin are the same name, the difference is that Marcin is
a Polish version - this is the correct spelling as far as Polish is concerned.
It is like John and Johann I guess; or Paul and Pavel (Pavel is Czech
here)
There are issues with names sometimes. eg. I can say that I am Maciej or
I can say I am Maciek. And it is perfectly fine. No spelling mistakes
there.
Regards,
Maciej
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Geert.
>>I mean: who makes a spelling error in his own first name? ;-)
>
> I don't think so: both `c' and `t' are (different) ASCII-transcripts of the
> actual non-ASCII character that should have been there. Yes, UTF-8 to US-ASCII
> is lossy and imprecise ;-)
Actually "c" in Marcin is correct in that place.
If I'm not mistaken Marcin is from Poland (or his father, or ..)
and in the polish language if you want to write the "ch" sound
(ch as in check) you write a c with an apostrofe above it if the
following letter is not a, e, i, o, u. If it IS one of those you
write "ci" instead instead of "c with an apostrofe".
Ciemno (dark).
,
Cma (a type of bug).
So, no, his name was not spelled wrong :)
Same goes for a few other characters as well.
Pronounce his name and it becomes clear why. Mar (ch) in.
Ci is a LONG sound.
,
C is a short sound. So Marcin would be pronounced Mar (ch) n.
Compare saying Check or Chck. Same thing.
// Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
iD8DBQFCXPqEBrn2kJu9P78RApGGAJ9ltnwuDCNZj4ykTkhvQcPZOEe+wwCglrjT
novruf57Yclv7kFlTty5hb8=
=qxmZ
-----END PGP SIGNATURE-----