From: Artem Bityutskiy <dedekind@infradead.org>
To: haver@vnet.ibm.com
Cc: "Artem B. Bityutskiy" <dedekind@oktetlabs.ru>,
"Monte K. Copeland" <catboat@texas.net>,
Andreas Arnez <arnez@de.ibm.com>,
MTD Mailinglist <linux-mtd@lists.infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Alexander Schmidt1 <ALEXSCHM@de.ibm.com>
Subject: Re: ubi-utils: Moving mkpfi, pfiflash, ... to old-tools
Date: Tue, 19 Feb 2008 11:34:17 +0200 [thread overview]
Message-ID: <1203413657.3758.25.camel@sauron> (raw)
In-Reply-To: <1203353343.8085.48.camel@august>
On Mon, 2008-02-18 at 17:49 +0100, Frank Haverkamp wrote:
> I talked to Artem. He told me that the tools had deficiencies that
> prevented him using them. 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.
>
> Of course it would be nice, if we could move the tools back even before
> the fixup, to avoid changing our build scripts. Let us discuss that with
> Artem tomorrow.
I can return the tools to the state they were before I touched them, is
it OK for you?
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2008-02-19 9:36 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
2008-02-19 9:34 ` Artem Bityutskiy [this message]
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=1203413657.3758.25.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