From: Artem Bityutskiy <dedekind1@gmail.com>
To: Ketil Froyn <ketil@froyn.name>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Matthieu CASTET <matthieu.castet@parrot.com>,
Mike Frysinger <vapier.adi@gmail.com>
Subject: Re: Suggested patch: reset errno after isatty()
Date: Sat, 13 Nov 2010 13:55:38 +0200 [thread overview]
Message-ID: <1289649338.2218.42.camel@localhost> (raw)
In-Reply-To: <1289646433.2218.22.camel@localhost>
On Sat, 2010-11-13 at 13:07 +0200, Artem Bityutskiy wrote:
> On Sun, 2010-11-07 at 23:36 +0100, Ketil Froyn wrote:
> > On Sat, Nov 6, 2010 at 9:54 AM, Mike Frysinger <vapier.adi@gmail.com> wrote:
> > >
> > > doesnt libmtd provide read functions already ?
> > > -mike
> >
> > I'm not familiar with libmtd, but the latest release (v1.4.1) just did
> > it itself with pread, and since that failed I fixed it.
> >
> > The new code in the repo, which appears to use libmtd, didn't work for
> > me, and the fix appeared more complicated. My patch is for v1.4.1,
> > which should also make it easier to integrate for package maintainers,
> > if they wish, pending a working rewrite.
>
> Ketil, you have a point,
>
> however, Mike is right, fixes should be back-ports, or if you fix a
> problem in the older release, you should fix it in the master branch as
> well, or show that it does not exist in the master branch. This is the
> only way it is possible to keep development under control.
>
> We really need to be sure that whatever is fixed in older releases is
> also fixed in the newer. Yes, this is more work for you but hey, I'm
> also doing this stuff in my spare time.
BTW, with patches from Brian Norris which I just pushed the master
branch may work better for you.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-11-13 11:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 14:37 Suggested patch: reset errno after isatty() Ketil Froyn
2010-11-03 8:23 ` Matthieu CASTET
2010-11-03 13:16 ` Ketil Froyn
2010-11-06 8:54 ` Mike Frysinger
2010-11-07 22:36 ` Ketil Froyn
2010-11-09 9:40 ` Mike Frysinger
2010-11-13 11:07 ` Artem Bityutskiy
2010-11-13 11:55 ` Artem Bityutskiy [this message]
2010-11-17 15:50 ` Ketil Froyn
2010-11-18 11:13 ` Ketil Froyn
2010-11-24 7:50 ` Mike Frysinger
2010-11-24 9:59 ` Ketil Froyn
2010-11-24 14:12 ` Artem Bityutskiy
2010-11-24 14:30 ` Ketil Froyn
2010-11-24 21:36 ` Mike Frysinger
2010-11-25 8:58 ` Ketil Froyn
2010-11-29 15:07 ` Artem Bityutskiy
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=1289649338.2218.42.camel@localhost \
--to=dedekind1@gmail.com \
--cc=ketil@froyn.name \
--cc=linux-mtd@lists.infradead.org \
--cc=matthieu.castet@parrot.com \
--cc=vapier.adi@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).