From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Aleksander Sanochkin <asanochkin@lnxw.com>
Cc: dwmw2@infradead.org, linux-mtd@lists.infradead.org
Subject: Re: JFFS1/MTD bug-fixes
Date: Fri, 7 Dec 2001 16:40:41 +0100 [thread overview]
Message-ID: <20011207164041.B25252@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0112070502020.12712-100000@newbast.lynuxworks.com>; from asanochkin@Lnxw.COM on Fri, Dec 07, 2001 at 05:07:18AM -0800
Hi!
> No, I didn't apply your patch actually. What I meant was that your changes
> to the MTD code are quite significant, and merging them with our updates
> to MTD doesn't appear to be harder than doing so with the current MTD
> code.
Sneaky one, now I understand. But merging my changes with the current
MTD code is finished, whereas merging them with your updates is new
work to be done.
The real question is, which patch will be merged first. If you are
second, the work is on you. ;-)
But as I already said, I will try to do this around Christmas. My
laptop is ordered, better wish me luck that it arrives in time.
Jörn
--
Treating your users as co-developers is your least-hassle
route to rapid code improvement and effective debugging.
next prev parent reply other threads:[~2001-12-07 15:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 13:07 JFFS1/MTD bug-fixes Aleksander Sanochkin
2001-12-07 15:40 ` Jörn Engel [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-07 13:11 Aleksander Sanochkin
2001-12-07 15:34 ` Jörn Engel
2001-12-04 16:36 Aleksander Sanochkin
2001-12-04 22:18 ` Jörn Engel
2001-12-04 16:30 Aleksander Sanochkin
2001-12-04 22:44 ` Jörn Engel
2001-12-03 15:36 Aleksander Sanochkin
2001-12-03 15:55 ` David Woodhouse
2001-12-04 9:07 ` Jörn Engel
2001-11-30 17:29 Aleksander Sanochkin
2001-12-01 10:47 ` David Woodhouse
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=20011207164041.B25252@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=asanochkin@lnxw.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
/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