public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Ilija Kocho <ilijak@siva.com.mk>
To: Will Wagner <will_wagner@carallon.com>
Cc: eCos Developers <ecos-devel@ecos.sourceware.org>
Subject: Re: Patches
Date: Tue, 20 Sep 2011 19:35:00 -0000	[thread overview]
Message-ID: <4E78EAF1.10305@siva.com.mk> (raw)
In-Reply-To: <4E7856BC.7000500@carallon.com>

On 20.09.2011 11:02, Will Wagner wrote:
> Hello,
>
> I have quite a long list of patches I'd like to submit. What is the
> preferred method? Patches to the mailing list or bugs in bugzilla?

Bugzilla is the method:
http://ecos.sourceware.org/fom-serv/ecos/cache/45.html

Hint: You can attach more than one patch to a Bug, a good way to group
them in some logical order.

I hope this helps.

Ilija

      reply	other threads:[~2011-09-20 19:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-20  9:03 Patches Will Wagner
2011-09-20 19:35 ` Ilija Kocho [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=4E78EAF1.10305@siva.com.mk \
    --to=ilijak@siva.com.mk \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=will_wagner@carallon.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).