From: John Dallaway <john@dallaway.org.uk>
To: Stephen Polkowski <stephen@centtech.com>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: Question regarding patches
Date: Thu, 30 Jun 2011 20:59:00 -0000 [thread overview]
Message-ID: <4E0CE3A3.9090106@dallaway.org.uk> (raw)
In-Reply-To: <4E0CDCD8.3000202@centtech.com>
Hi Stephen
Stephen Polkowski wrote:
> I submitted a patch about a week ago for the Via Rhine (10/100)
> driver [1001269]. There was a small bug that required a simple fix. I
> listed the patch under Ethernet, but now I'm wondering if I should have
> listed it under "Patches and Contributions"?
Submitting patches against the "Patches and Contributions" component is
preferable, but we are certainly aware of your patch.
> Am I following the correct procedures to get this patch into the CVS
> tree? How long does it usually take to get a change into CVS?
That's a difficult question to answer. It all depends on the complexity
of the patch, the current workload of the eCos maintainers and whether
any patch revision is necessary. Anything from a few hours to many months.
> The reason I
> ask is that I'm planning a REDBOOT rhine package for IA32. I already
> have it working my office. I just wanted to see how my simple Rhine
> patch worked out before submitting a REDBOOT rhine package.
>
> Ultimately, I want to release a new Via Velocity (Gigabit) ethernet
> driver for eCos. So, I'm getting my feet wet with some small changes
> first.
Great! I do recommend that you get the copyright assignment in place
early as this can take quite a while to process. Ref:
http://ecos.sourceware.org/contrib.html
Thank you for contributing...
John Dallaway
eCos maintainer
http://www.dallaway.org.uk/john
prev parent reply other threads:[~2011-06-30 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 20:31 Stephen Polkowski
2011-06-30 20:59 ` John Dallaway [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=4E0CE3A3.9090106@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=stephen@centtech.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 read-only IMAP folder(s) and NNTP newsgroup(s).