From: "Michael Mattsson" <michael@kyrana.com>
To: <gentoo-dev@gentoo.org>
Subject: RE: [gentoo-dev] GCC 3.1/3.2
Date: Mon, 29 Jul 2002 03:14:21 -0400 [thread overview]
Message-ID: <006701c236cf$9027c1d0$0a01a8c0@neptune> (raw)
> Most of my patches are actually in the Gentoo source tree. When you
> emerge a package and you see a line that it's patching the
> source code right after unpacking the source... that's possibly one of
> the gcc-3.1 patches. As far as where I send the patches to... I go to
the
> maintainer's website and e-mail it to him/her and also explain all my
> changes.
Gentoo patches 3rd party apps for new GCC versions? I would have
expected the original package author to be doing that, not people from a
particular distro.
> And if you wanna see lots of kernel hacks at patches by us Gentoo
> people... try mjc-sources
Is gentoo developing the patches in mjc, or just including them? Most
of the patch authors I recognize from the linux-kernel mailing list - do
many of them work with gentoo?
Michael Mattsson
Kyrana Inc.
michael@kyrana.com
next reply other threads:[~2002-07-29 7:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-29 7:14 Michael Mattsson [this message]
2002-07-29 10:09 ` [gentoo-dev] GCC 3.1/3.2 Matthew Kennedy
-- strict thread matches above, loose matches on Subject: below --
2002-07-29 7:28 Thomas Beaudry
2002-07-28 22:01 Thomas Beaudry
2002-07-28 5:07 Matthew J. Turk
2002-07-28 10:44 ` Bart Verwilst
2002-07-28 13:25 ` Doug Goldstein
2002-07-28 17:26 ` Terje Kvernes
2002-07-28 17:44 ` Matthew J. Turk
2002-07-28 18:27 ` Michael Mattsson
2002-07-28 22:16 ` Doug Goldstein
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='006701c236cf$9027c1d0$0a01a8c0@neptune' \
--to=michael@kyrana.com \
--cc=gentoo-dev@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