Josselin Mouette <j...@debian.org> wrote:
> Please don???t forward private replies to a public mailing list: this is
> very rude behavior.
Well, this is an open discussion and I see no reason not to share your rude
replies with others.....
> Le jeudi 26 février 2009 à 17:08 +0100, Joerg Schilling a écrit :
> > **************
> > If you are using a coding other than 7-Bit ASCII or ISO-8859-1, you need to
> > properly declare your transfer encoding. Please fix your mail client!
> > **************
>
> The email you are replying to declares:
>
> Content-Type: multipart/signed; micalg=pgp-sha1;
> protocol="application/pgp-signature"; boundary="=-QLLn2OxCNRVAvKDPZ8Na"
> [snip]
> --=-QLLn2OxCNRVAvKDPZ8Na
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
This is not true, your mail does not contain the content encoding type line you
claim.
My mail (the one you did reply to) on the other side is correct:
...
In-Reply-To: <1235654190.5228.47.ca...@shizuru>
User-Agent: nail 11.22 3/20/05
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Return-Path: joerg.schill...@fokus.fraunhofer.de
So please fix your mailer
> > If you see problems with any frontend, you should make a bug report. The
> > original software works as documented. If there is any frontend does not
> > work, it
> > has been broken and needs to be fixed.
>
> Indeed, the frontends have all been fixed, by calling wodim instead of
> cdrecord. And now they work as expected.
If you believe that breaking a frontend is a godd idea, then you should
not be a maintainer.
> > There are many reports from people who replaced the fork by unmodified
> > original
> > software in order to finally be able to write CDs and DVDs.
>
> Please forward us such reports of people doing that successfully within
> Debian; this looks like a lot of fun. Not forgetting that distributing
> such solutions would violate the licensing of several of the frontends.
Please read the Debian bugtracking system for at least 70% of the typical well
known bugs in the fork...Note that you may need to check _all_ entries even
those declared as "closed" as many of them never have been fixed in the code.
> > > > wodim still has a lot more bugs than the outdated original it was based
> > > > on.
> > >
> > > Show them. Come on.
> >
> > I encourage you to read the Debian bug tracking system!
>
> Sorry, but simple reports are not convincing without analysis. Please
> show where the bugs come from, and explain why they don???t apply to
> cdrecord.
I recommend you to read the Debian bug tracking system. If you do not
understand the reports and their background, you do not seem have the
needed skills for a dicussion on the problems.
The bug reports in the Debian bug tracking system do not apply to cdrtools
because they either have been introduced by Eduard Bloch and thus never have
been in the original software or because they have been fixed years ago in the
original software but obviously not in the fork.
Jörg
--
EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
j...@cs.tu-berlin.de (uni)
joerg.schill...@fokus.fraunhofer.de (work) Blog:
http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
