From: Artem Bityutskiy <dedekind@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Artem B. Bityutskiy" <dedekind@oktetlabs.ru>,
"Monte K. Copeland" <catboat@texas.net>,
MTD Mailinglist <linux-mtd@lists.infradead.org>,
Andreas Arnez <arnez@de.ibm.com>,
Alexander Schmidt1 <ALEXSCHM@de.ibm.com>,
Frank Haverkamp <haver@vnet.ibm.com>
Subject: Re: ubi-utils: Moving mkpfi, pfiflash, ... to old-tools
Date: Wed, 20 Feb 2008 12:10:00 +0200 [thread overview]
Message-ID: <1203502200.3758.31.camel@sauron> (raw)
In-Reply-To: <alpine.LFD.1.00.0802182214000.7583@apollo.tec.linutronix.de>
On Mon, 2008-02-18 at 22:26 +0100, Thomas Gleixner wrote:
> I really give a sh*t whether Artem can use them or not. He is not the
> center of the universe. If he needs them changed, then he should send
> a patch or a suitable replacement for the tool, which does not force
> others to fixup their scripts and build tools for no benefit. This is
> not a sandbox, this are tools used in production environments.
>
> Artem, please stop this nonsense right now. You can create your own
> world if you have the urge to do so, but please keep stuff others use
> intact. This "I don't like that old crap" attitude is an arrogant and
> at the same time ignorant childish behaviour, which has no place in a
> serious project.
>
> > E.g. that he could not put the vid-hdr the
> > offset he wanted it to put. He promissed me to write up the deficiencies
> > so that we can work on them. I am sure that after fixing, we can move
> > the tools back to their old location.
>
> No, they go back to their place immediately, period.
>
> Yours even more grumpy,
I apologize for this. Indeed that was not nice and arrogant. The tools
are returned to their previous place.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2008-02-20 10:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 13:49 ubi-utils: Moving mkpfi, pfiflash, ... to old-tools Frank Haverkamp
2008-02-18 15:28 ` Artem Bityutskiy
2008-02-18 16:01 ` Thomas Gleixner
2008-02-18 16:49 ` Frank Haverkamp
2008-02-18 16:53 ` Josh Boyer
2008-02-19 8:47 ` Frank Haverkamp
2008-02-19 12:29 ` Josh Boyer
2008-02-19 12:56 ` Frank Haverkamp
2008-02-18 21:26 ` Thomas Gleixner
2008-02-20 10:10 ` Artem Bityutskiy [this message]
2008-02-19 9:34 ` Artem Bityutskiy
2008-02-19 9:57 ` Frank Haverkamp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1203502200.3758.31.camel@sauron \
--to=dedekind@infradead.org \
--cc=ALEXSCHM@de.ibm.com \
--cc=arnez@de.ibm.com \
--cc=catboat@texas.net \
--cc=dedekind@oktetlabs.ru \
--cc=haver@vnet.ibm.com \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox