From: Matt Porter <mporter@kernel.crashing.org>
To: Marius Groeger <mgroeger@sysgo.com>
Cc: Embedded PPC Linux list <linuxppc-embedded@ozlabs.org>
Subject: Re: what is the protocol for getting patches into the tree?
Date: Mon, 4 Oct 2004 09:43:38 -0700 [thread overview]
Message-ID: <20041004094338.E11487@home.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0410041809210.11176@mag.sysgo.com>; from mgroeger@sysgo.com on Mon, Oct 04, 2004 at 06:11:05PM +0200
On Mon, Oct 04, 2004 at 06:11:05PM +0200, Marius Groeger wrote:
> On Mon, 4 Oct 2004, Matt Porter wrote:
>
> > Yes, submit it over and over until there is some feedback. argue
> > or follow the feedback...eventually it will go in unless it's not
> > a desirable change. If no feedback, keep submitting until the
> > maintainer has time to look at it.
>
> Well, how about asking Russel to hand out the scripts for
>
> http://www.arm.linux.org.uk/developer/patches/
>
> Would this help?
No, it just provides a web-based interface to what is handled
via mailing lists. It's just as easy for a maintainer to get
busy and not ack a patch submission on a web-based system as well.
I suspect that this is an 8xx-specific problem. The source of
the problem is that 8xx has been undermaintained for some time
and it only recently has gained a new maintainer.
-Matt
next prev parent reply other threads:[~2004-10-04 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 15:24 what is the protocol for getting patches into the tree? Robert P. J. Day
2004-10-04 15:48 ` Matt Porter
2004-10-04 16:11 ` Marius Groeger
2004-10-04 16:43 ` Matt Porter [this message]
2004-10-05 15:02 ` Tom Rini
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=20041004094338.E11487@home.com \
--to=mporter@kernel.crashing.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mgroeger@sysgo.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).