All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alain Knaff <alain@knaff.lu>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	the arch/x86 maintainers <x86@kernel.org>,
	greg@kroah.com, Roland <devzero@web.de>
Subject: Re: The bzip2/lzma patches
Date: Wed, 31 Dec 2008 15:22:58 +0100	[thread overview]
Message-ID: <495B8042.1080001@knaff.lu> (raw)
In-Reply-To: <20081231134218.GC2388@uranus.ravnborg.org>

Sam Ravnborg wrote:
> Hi Alain.
> 
>> If I may suggest something: what if *YOU* provided a patch (or series of
>> patches, or whatever you like) complying to your high stylistic
>> requirements
> 
> hpa does not have any high stylistic requirments he just have good taste.
> He simply ask you do do a better job and if you want this in then
> please follow his advice.
> 
> Asking him to do the job you want to have done is just not the way forward.
> 
> 	Sam

Thanks for the advice. You're right, this is not the way forward. I must
admit that I did indeed an huge mistake with this patch.

I've initially developed it a couple of years ago for use in udpcast.
Once done, regular attention was needed for it to adapt it to new
kernels. At one point in time (this September), I figured that I could
save that maintenance effort by getting it integrated into the mainline
kernel. At the same time, I figured, other developers of embedded
systems could profit from it. A win-win situation. Or so I thought.

However, now that I look back on the 3 past months, I figure that the
amount of effort that I poured into this was disproportionate compared
to what I used to spend on maintaining it out of kernel. Even if I
continued evolving it until the end of my life, I would spend _less_
time on it than I did in the last 3 months.

My conclusion is that I'll continue like I did before last summer: to
maintain it on my own website (http://udpcast.linux.lu/source.html)
along with udpcast.

Anybody is still welcome to use it as he sees fit. If a brave soul with
more patience than me wants to plead with the powers-that-be to get it
into official kernel, he has my support. But for myself, I give up on
this quest, it is simply too much hassle to be worthwhile...

Regards,

Alain


      reply	other threads:[~2008-12-31 14:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-31  2:47 The bzip2/lzma patches H. Peter Anvin
2008-12-31  8:47 ` Alain Knaff
2008-12-31 13:42   ` Sam Ravnborg
2008-12-31 14:22     ` Alain Knaff [this message]

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=495B8042.1080001@knaff.lu \
    --to=alain@knaff.lu \
    --cc=devzero@web.de \
    --cc=greg@kroah.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.