From: "Marijn Schouten (hkBst)" <hkBst@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] guidline to set a timeline of removal of ebuild from stable tree
Date: Tue, 12 Jun 2007 13:09:12 +0200 [thread overview]
Message-ID: <466E7ED8.7020006@gentoo.org> (raw)
In-Reply-To: <C2176D56-AD3C-4708-ADFB-8DF795B56275@cilly.mine.nu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
cilly wrote:
> please, understand that I do not want to `blame` any developer, unless
> it is discussed here with a final solution. Since I am not a gentoo-dev,
> some of the devs `may not understand` my concerns and probably `feel
> offended`.
Hi Cecilia,
Nobody will feel offended by your bug report. I'm asking you to go into
specifics precisely because I want to better understand what the exact problem
is. Or you could start using lilypond and tell me all that is wrong with it (a
lot). When 2.10.26 comes out in probably a few days I'll be removing all other
testing versions, except 2.11.26, because they have problems with the newest
fontforge. I hope 2.10.26 will be good enough to be stabled.
Marijn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGbn7Yp/VmCx0OL2wRAjM2AJ0UdBKDsb+u0CVHvttKwAakqKvLgACfYer9
9J70SOJpZNkMNIkXe30OnRo=
=9nCO
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-06-12 11:12 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 9:40 [gentoo-dev] guidline to set a timeline of removal of ebuild from stable tree cilly
2007-06-12 9:49 ` [gentoo-dev] " Christian Faulhammer
2007-06-12 9:53 ` cilly
2007-06-12 9:59 ` [gentoo-dev] " Luca Barbato
2007-06-12 10:04 ` Fernando J. Pereda
2007-06-12 10:01 ` Fernando J. Pereda
2007-06-12 10:14 ` cilly
2007-06-12 10:21 ` Fernando J. Pereda
2007-06-12 10:30 ` cilly
2007-06-12 10:40 ` Marijn Schouten (hkBst)
2007-06-12 10:48 ` cilly
2007-06-12 11:09 ` Marijn Schouten (hkBst) [this message]
2007-06-12 10:36 ` Richard Freeman
2007-06-12 10:46 ` Fernando J. Pereda
2007-06-12 10:53 ` cilly
2007-06-12 10:59 ` cilly
2007-06-12 11:27 ` Luca Barbato
2007-06-12 11:37 ` cilly
2007-06-12 11:29 ` Christoph Mende
2007-06-12 11:38 ` cilly
2007-06-13 14:35 ` Robert Buchholz
2007-06-13 14:58 ` Brian Harring
2007-06-12 16:55 ` [gentoo-dev] " Duncan
2007-06-13 14:44 ` banym tuxaner
2007-06-12 11:03 ` [gentoo-dev] " Fernando J. Pereda
2007-06-12 11:08 ` cilly
2007-06-12 16:05 ` Luis Francisco Araujo
2007-06-12 10:48 ` Luca Barbato
2007-06-12 10:50 ` cilly
2007-06-12 11:21 ` Petteri Räty
2007-06-12 11:50 ` cilly
2007-06-12 11:00 ` Marijn Schouten (hkBst)
2007-06-12 11:25 ` [gentoo-dev] " Christian Faulhammer
2007-06-12 11:52 ` cilly
2007-06-12 12:55 ` [gentoo-dev] " Marius Mauch
2007-06-12 12:59 ` cilly
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=466E7ED8.7020006@gentoo.org \
--to=hkbst@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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